egg-di | Dependency injection lib for Egg.js | Dependency Injection library

Muonic, based on the documentation, appears to be made for Linux, while you are trying to install it on a Windows machine. This is likely why the path variable is a nonetype and is causing the problem.

Based on feedback from a helpful user, I eventually arrived at a less hack'y solution. Unfortunately, the discussion went AWOL because of an unhelpful user, who responded with pip install -U numpy, waited for me to figure it out, edited their answer and requested I accept it. Upon being denied, the answer and comment thread vanished. I don't even remember your name, helpful user, so I can't credit you for the tip.

Apparently ReadTheDocs uses an old pip, and requiring pip>=19.0 makes scikit-learn not install from source. As such, I added that line to docs/requirements.txt, which I had previously set up to be a ReadTheDocs requirement file. This resulted in some progress - now rather than scikit-learn complaining about numpy, it was numba. Still, some synapses connected, and I just handled any dependency problems that arose via docs/requirements.txt, the final contents of which are:

from another post seemed irrelevant i figure out the solution

ImportError: No module named zbar on Linux Mint

however only zbar-tools not enough for the good result, i put in

sudo apt-get install zbar-

and press the TAB then found zbar-dbg, just for a try, it really worked.

sudo apt-get install zbar-tools zbar-dbg

it really struck me while gcc errors caused by zbar problem indeed. maybe some inspire for the similar problem, so i put it here.

Looks like a recent version of setuptools was missing. After adding it to the Dockerfile, the pip way of installing pylint works just fine.

Try

apt-get --auto-remove remove python-openssl

followed by pip install pyopenSSL

Since it succeeds the second time around, my best guess is that packages are not installed in the intended order. Or not installed completely before the next package is processed.

Based on the log file snippet, it's not clear what the attempted installation order was. The error message shown seems to be for cppyy only, but all it says is that if fails b/c it can't find eggs for CPyCppyy, so the relevant error message should come from that one. Note that building of wheels and eggs is disabled, because pip does not resolve dependencies before attempting to build those. Meaning that such builds would either fail, or use an old install if there happens to be one (which is even worse).

Anyway, the order has to be cppyy-cling, cppyy-backend, CPyCppyy, cppyy. (The reasoning behind the split is explained here: https://cppyy.readthedocs.io/en/latest/packages.html#package-structure.) Each package needs to be fully installed before the next can proceed: the cling-config script (provided by cppyy-cling) is used to propagate compiler flags (in particular it propagates which C++ standard should be supported), so that needs to be available.

The recently released version 6.0 of more-itertools seems to have introduced this bug. The following should hot-fix it:

It took some digging to find the answer. I am posting the answer here for the sake of completeness and searchability :).

The python command at the beginning of easy-install.pth is called prelude and the one at the last line is called postlude (in setuptools code).

As is expected easy_install re-writes the PathDistributions, i.e. easy-install.pth, if you installation leads to removal of an old package and installation of your new package.

Now if you want to include the prelude and postlude the code expects SETUPTOOLS_SYS_PATH_TECHNIQUE environment property to be set to rewrite (default value is raw). To put it more concretely, following commands fixed the problem:

The solution was (in retrospect) pretty silly. My dependency package was missing this line in its setup.py: