I'm maintaining a multi-user conda environment, and I'm looking at adding a conda package whose build script does
python setup.py install
it looks like the package just creates two files
package.pth
package*.egg
in my environments site-packages area.
The .pth file looks benign, it just lists the egg file, that is no other PYTHONPATH manip via site.py's processing of it (like
conda-verify flags easy_install.pth files that can collide with one another, but I guess it doesn't complain about egg files in general), however I've got the sense that egg files and .pth files are not a "best practice" for conda, with the exception of using .pth for develop versions.
Is this wrong? If switching to
python setup.py install --single-version-externally-managed
is a best practice for conda packaging, I'm sure the author would appreciate knowing.
For example, does conda-forge have stricter rules before accepting packages? Like, no egg files? I don't have enough knowledge of egg files to evaluate, but my feeling is they are problematic, I'd rather see the python package in its own directory.
best,
David