wcwidth | Python library that measures the width of unicode strings

Yes I wanted to thank everyone for their help. While I have a time lime for my project I will dit the post to see my work around as well. Thanks.

You have installed an extremely old version of OSMnx. Your conda list output shows you have version 0.7.3 installed, and that was released 3 or 4 years ago. It's so old that it's incompatible with the modern features of GeoPandas and pyproj, including the modern CRS object that's causing your error. I'm not clear how you did it! My best guess is you installed using one of the old tags on this page, which do point to version 0.7.3.

This should be fixed by removing the old environment and then following the installation instructions here, like:

Channel pypi means that the package was installed with pip. You may need to upgrade it with pip as well

Figured it out.

What works:

The reason is that the python used by the internal terminal of VS Code is different from the python environment you currently select in VS Code (shown in the lower left corner of VS Code).

I noticed that you are using the powershell terminal, which does not automatically activate the conda environment by default in VS Code.

1. Please select conda environment in VS Code, it will be displayed in the lower left corner of VS Code. (F1, Python: Select Interpreter)

2. Please enter "Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process" in the VS Code terminal, and then reopen the VS Code terminal (Ctrl+Shift+`). When using the command "python --version", the python version it displays is the same as the one displayed in the lower left corner.

3. If the module is not installed in this environment, please follow it. (pip install pandas)

Update:

In addition, please try to use other terminals, such as the 'cmd' terminal. Can I use Cmder's shell with the terminal on Windows?

Reference: Python environments in VS Code.

At the end, I ended up solving this by rolling back the changes I made using conda list --revisions to find out until which previous set up I had to roll back to, then afterwards I ran conda install --revision N (where N is the revision you want to trace back to). Suppose the changes you made are rev 4, you want to undo them, and sit back again under rev 3 (your previously "known and working" environment you had), so you run conda install --revision 3 for that case.

Afterwards I re-installed pandas_datareader with python -m pip install pandas-datareader and everything went good again.

Thanks anyways and I hope if someone else runs into this issue, can find this post valuable.

• conda only keeps track of the packages it installed
• pip freeze will give you the packages that were either installed using pip package manager or they used setuptools in their setup.py so conda build generated the egg information.

conda vs pip

Downgrading the pip may fix this issue, you can check this out: conda issues

I don't know if this will come useful to you. I recently had a problem with the celery worker getting stuck and blocking the line. The thing is that celery is supposed to automatically spawn as many workers as the server has CPUs, but i found that number not to be enough for the use i was making of it.

I solved the problem adding --concurrency=10 in the celery execution line in my container commands. You can add this flag manually if you start celery from the CLI.

The complete execution command is this:

/path/celery -A my_proj worker --loglevel=INFO --logfile=/var/log/celery.log --concurrency=10

This spawns 10 workers no matter what.

From the list of libraries, it looks like you've installed CPU only version of the Pytorch.