working_set | makes searching , and using search results | Text Editor library

Did you try to install it using Snap? Maybe it can solve the problem because it seems to have a conflict with python 3 packages:

So my suggestion is to conceptually split this problem into two parts.

First sub-problem: determine all of the modules imported in pkg-foo. Let's use mod_foo to be some arbitrary imported module in pkg-foo

Second sub-problem: determine if any mod_foo are from pkg-block. If none of these modules are in pkg-block, pass the unit test, else, fail the unit test.

To solve the first sub-problem you can use the class modulefinder.ModuleFinder. As shown in the example from the documentation, you can do modulefinder.ModuleFinder.run_script(pathname) for each module in pkg-foo. Then you can get the module names by grabbing the keys from the dict modulefinder.ModuleFinder.modules. All of these modules will be your mod-foo modules.

To solve the second sub-problem, you can use mod_foo.__spec__ As mentioned here, mod_foo.__spec__ will be an instance of 'importlib.machinery.ModuleSpec' which is defined here. As described in the documentation just linked to, this object will have the attribute name which is:

A string for the fully-qualified name of the module.

Therefore we need to check to see if pkg-block is in the fully qualified name given by mod_foo.__spec__.name for each mod_foo.

Putting this all together, something along the lines of the following code should do what you need:

As others have stated, Python 3.10 is not currently compatible with Matplotlib. You need to install and use Python 3.9 until it is supported. Until then you have a few options:

You can use the Python Launcher for Windows (py.exe) script to choose which Python version to run like so:

py.exe script help: py -h

List all installed versions py -0

Use a specified version py -3.9

e.g. 1 Create a virtual environment using python 3.9 py -3.9 venv .venv

e.g. 2 install matplotlib with pip using python 3.9 py -3.9 -m pip install matplotlib

On Linux you can run whatever Python version you like like so:

python3.9

You can set up a local (your working directory and all sub-directories) virtual environment that will use your specified version like so:

python3.9 -m venv .venv

Which will set the version of python used to 3.9 while in the local directory, and allow you to type python instead of python3.9 each time you need it.

Another relevant and helpful post by Rotareti here.

Please note that I have not described how to activate and use Python Virtual Environments here in detail, for more information on using them read the python docs.

Reference this answer if you're interested in installing a matplotlib release candidate.

Not totally sure, but I ran into the same issue. After some digging and testing I think I've found out that Matplotlib, and pylab aren't compatible with python3.10 yet. For the time being I've kept python3.9 along with 3.10 so whenever I use matplotlib, numpy, or pylab, I just use version 3.9.

For your instance, either the Google Cloud packages or the Python installation or both are broken. This issue prevents you from being able to log in.

I recommend that you create a new instance and move the persistent disks from the broken instance to the new instance.

STEP 1:

Create a new instance in the same zone. A micro instance will work.

STEP 2:

Open a Cloud Shell prompt (this also works from your desktop if gcloud is set up). Execute this command. Replace NAME with your instance name (broken system) and DISK with the boot disk name and ZONE with the zone that the system is in:

How did you install Spyder? Did you use the installer or install it with pip/conda? Where are you installing your packages - what environment?

It appears that the environment where you install packages with pip (e.g. lxml) is different than what Spyder is running with. See https://docs.spyder-ide.org/current/faq.html#using-existing-environment

Note that for Spyder to work with other environments you need to install spyder-kernels in this environment (e.g. pip install spyder-kernels)

try being explicit in the version of python you are using and install using -m pip instead

You are installing the wrong package. Change dotenv to python-dotenv in your requirements.txt file. See this issue for more information. https://github.com/theskumar/python-dotenv/issues/113

I found a workaround. You can install almost any python lib as a package. Easier to do it like this then to fiddle with python as I don't use it very often.