pip freeze includes the current directory, if there is an egg-info.

[tomprince]

At least when the current directory is a git repository. In addition, it treats as something wanting -e and also gives it the wrong #egg (it appears to give it <package-name>-<git-branch> as the #egg).

[tomprince]

The egg-info part is #2926

[dstufft]

I believe that this can be solved by just skipping . when iterating over sys.path looking for installed projects.

[jadkik]

Can this be fixed by adding a custom skip list in addition to the standard ('pip', 'setuptools', 'distribute', 'wheel') and expose that in the command arguments?

There may be several internal development packages that are installed in a single virtual environment.

[kaikulimu]

Hi, I am from PyPA Sprint Weekend at Bloomberg (2018), and I will work on this!

[kaikulimu]

Add PR: #5951

[gokcennurlu]

How can we reproduce this, by the way?

[kynan]

@pradyunsg Please move to in progress

[DavidBord]

@pradyunsg I cannot seem to reproduce. The steps I did:
checkout a git project of a python package
python setup.py bdist_wheel --universal
pip freeze - didn't see the egg.info
cd dist
pip freeze - didn't see the egg.info
cd ../
mv dist/*.egg-info .
pip freeze - didn't see the egg.info

Please advice

[gutsytechster]

@pradyunsg, is this issue resolved. I see a PR closed regarding this #5951. Does the change in this PR is what intended to be done?

[uranusjr]

It’s not fixed; the PR was closed because it was abandoned in a non-mergeable state. Feel free to re-apply the changes and submit a new PR against master.

[gutsytechster]

Great! I'd like to work on it. :)

[uranusjr]

Cross-referencing #7731; this might be the reason why some had trouble reproducing the issue.

[gutsytechster]

@uranusjr Thanks for the pointer. I was able to reproduce the same behaviour with pip freeze.

[gutsytechster]

Is it about providing the same behaviour for pip freeze, when used with and without python -m? As without python -m, pip does not include the current directory. But with it, pip does.

Also, I tried to test my change first by installing an updated version of pip by running the command python setup.py install, within the virtual environment.

So, when I do pip --version within my virtual-env, I get pip 20.1.dev0 from /home/gutsytechster/miniconda3/envs/pip-env/lib/python3.6/site-packages/pip-20.1.dev0-py3.6.egg/pip (python 3.6) i.e. it does fetch pip from the installed package. However, when trying to get the version using python -m pip --version, I get pip 20.0.2 from /home/gutsytechster/miniconda3/envs/pip-env/lib/python3.6/site-packages/pip (python 3.6). Why is there a difference of version?

[uranusjr]

Is it about providing the same behaviour for pip freeze, when used with and without python -m? As without python -m, pip does not include the current directory. But with it, pip does.

That’s (what I consider) correct, but we’d need to first found out what causes this different behaviour before we decide on the solution.

For the experiement, the difference is due to Setuptools (or distutils?) uses a different logic to load the module in the the entry point script (see cat /miniconda3/envs/pip-env/bin/pip) . It’s now condiered a bad idea so pip does not do that (the one it uses is more similar to python -m). The “solution” is to just not run setup.py install at all, it’s a bad idea.

[gutsytechster]

I run python setup.py install to just install my changes to the pip within virtual environment. so that I can test manually as well, the changes I've made. Is there some other way to achieve this?

[uranusjr]

You can replace that with pip install . (the last dot means pwd, not a period).

[gutsytechster]

Thank you! That really helped. python -m pip now also takes the pip version which I install via pip install .