iniconfig

I used pip install eth-brownie and it worked fine, I didnt need to downgrade. Im new to this maybe I could be wrong but it worked fine with me.

The error error: [Errno 2] No such file or directory: '/opt/anaconda3/lib/python3.8/site-packages/rtree/lib' was caused by py2app trying to build the program bundle using a non-existent interpreter. This means that even if you try to uninstall a manager like Anaconda, it still has option logs somewhere on your mac.

The fix:

1. Open the terminal and type the command type -a python.

• You will see similar lines

Build tags in you environment.yml are quite strict requirements to satisfy and most often not needed. In your case, changing the yml file to

Based on

The problem here is that I had broken dependencies which would not allow me to do any updates nor new installs.

This had to do with having packages from both conda and pip. Some of them play nice together, some don't.

My solution, was unfortunately, rather atomic. I deleted the environment and created a new one with Python 3.7. Upon doing that, I also added an extra conda channel conda-forge which I recommend instead of pip.

Once I did that I installed all the dependencies and packages using conda and it worked.

Here are the command I used:

geopandas 0.10.1

• have noted that your data is on kaggle, so start by sourcing it
• there really is only one issue shapely.geometry.MultiPoint() constructor does not work with a filtered series. Pass it a numpy array instead and it works.
• full code below, have randomly selected a point to serve as gpdPoint

Searching for the exception, leads to the corresponding eventlet issue: https://github.com/eventlet/eventlet/issues/687

The summary is that eventlet (0.32.0) is currently not compatible with Python 3.10 because it tries to patch types that have become immutable in Python 3.10.

Like with your requirements, it is good practice to be more specific with your Docker dependencies too. Today using the tag 3 for the Python Docker image will give you 3.10.0, unless it is using a cache. In the future it could be a different version. Since there is a compatibility issue with Python 3.10, use Python 3.9 - the currently latest Python 3.9 Docker tag is 3.9.7.

i.e. it should work once you change your first line of the Dockerfile to:

If you have a look for the base image, you could see it just be updated 27hours ago.

It is very likely that pip3 is pointing to a different python instance.

Imagine you had python, python3, python3.6 and python3.8 all installed on your system. Which one would pip3 install packages for? (who knows?)

It is almost always safer to do python3.8 -m pip list/install since you can be sure that python3.8 somefile.py will be using the same files you just saw. (even better, do python3.8 -m venv /path/to/some/virtualenv and then make sure that is activated, then you can be sure pip points to the same python)