New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pipupgrade incorrectly detects two pyenv-installed pip bins ('pip' & 'pip3'), from *single* Python install env, as from separate 'installed distributions' #62
Comments
reading
to limit to one executable, setting
but exec still detects TWO pip instances
as does
|
I believe that the
EDIT: Looking at the environment variables , it does not appear that any of them have anything to do with the pip path. |
+1, thx 4 the ref
sure seems like it should -- as most of the OTHER opt args' values have env var equivalents ... Still leaves the question -- should pipupgrade be 'smarter' in this case, where it's ONE installed distribution, with two differently-named, but otherwise identical,
pip instances? in the meantime, a simple py3 workaround, in bash profile, after init'ing pyenv, adding an alias
does the trick, using only the one pip* instance,
where
switches cleanly after switching py3 versions, as long as you re-source the profile. |
If anyone figures out a better way to manage this would be great! Prior to this, |
it ain't pretty, but hash checking
is at least conclusive for a given venv |
closing, why? fixed elsewhere? or WONTFIX? |
I could add the checksum. |
|
@pgnd the above solution seems limited to just |
ah, messy then ... |
However, I'll consider symlinks in this case. :) |
'do that voodoo that you do' ! |
Pending for release! |
@pgnd please update to |
incurrent pyenv
self-upgrade fails
looking in src
that's a different env, and when in THIS env, should be left alone trying instead with a pip upgrade of pipupgrade
|
hm, with two supposedly separate pyenv
where
part of the confusion, i think, arises from
|
i've installed python 3.8-dev via pyenv
for this installed env, pip & pip3 are identical
and function identically.
i.e., they're of the same 'installed distribution'.
i've pip-installed 'pipupgrade`
on exec, pipupgrade sees TWO 'installed distributions', one for each of the two identical/redudndant pip/pip3 instances
e.g.,
an upgrade will attempt, incorrectly, to install/upgrade for EACH of the detected pip instances -- 'pip' & 'pip3'
The text was updated successfully, but these errors were encountered: