pygments | Pygments code highlighting via Google App Engine | Code Inspection library

A workaround for my problem is to use opencv-python-headless headless instead.

You can change the default with of the images using \setkeys{Gin}{width=.8\linewidth} and boarders can be added with the floatrow package:

MarkupSafe (2.0.1) requires Python >= 3.6, so get a newer version of Python. PyPI

The problem isn't because you're replacing the default bindings. That's simply not how bindings work in tkinter. There are no bindings directly tied to the root widget or any other specific widget. Default bindings are implemented as bindings on "all" or on widget classes, not individual widgets.

They work fine if i bind it to the text widget but the last entered letter doesnt get highlighted.

That is because a binding on a widget happens before the default bindings. So, if you type "a", your code will be called before the code that inserts the letter "a".

There is a question on this site related to the order in which events are processed. While the answer is tied to an Entry widget, the exact same concept applies to all widgets. See this answer to the question Basic query regarding bindtags in tkinter

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:

Soleved! Thank you your advice, @krassowski!

I can have Jupyterlab load advanced settings when launching with {sys.prefix}/share/jupyter/lab/settings/override.json like below.

The rust dependency is bring by pywinpty that needs also MSVC. This package

PyWinpty allows creating and communicating with Windows processes that receive input and print outputs via console input and output pipes. PyWinpty supports both the native ConPTY interface and the previous, fallback winpty library.

Then it is not needed on stack heroku-20 that is Ubuntu.

Removing pywinpty from requirements.txt should help.

I was having the same issue due to a Pygments 2.3.1 version.

It seems that you are confusing the use-cases for PythonVirtualenvOperator and PythonOperator.

If you simply want to run a Python callable in a task (callable_virtualenv() in your case) you can use PythonOperator. In this case, it does not matter if you installed Airflow in a virtual environment, system wide, or using Docker.

What happens in your code is the following: PythonVirtualenvOperator creates another virtual environment (which is completely unrelated to the one in which you run Airflow), installs Airflow into it, and tries to import Variable. But this another Airflow installation is not configured and that is why you get those exceptions. You could set the AIRFLOW_HOME environment variable for this second Airflow installation to the same directory as used by the first Airflow installation, and this should actually work, but it looks like an overkill to me.

So, what you can do is install colorama into the same environment in which you installed Airflow and replace PythonVirtualenvOperator by PythonOperator.

BTW, those print() inside the callable would be redirected into a log file and not printed to terminal, so it probably does not make much sense to use colorama with them.