No python3 support?

[cefn]

I installed pip-autoremove using pip3 but unfortunately it isn't indicated anywhere that it's a Python2 only tool. Perhaps the github could be updated to indicate this, or the python3 version could be removed.

Initially pip-autoremove didn't work at all, since it had an undeclared dependency on Pypi 'testresources'. After I installed pip3 install testresources the utility would then run, but failed when attempting to run a pip autoremove operation...

$ pip-autoremove serial
serial 0.0.66 (/home/cefn/.local/lib/python3.6/site-packages)
    PyYAML 3.12 (/home/cefn/.local/lib/python3.6/site-packages)
    future 0.16.0 (/home/cefn/.local/lib/python3.6/site-packages)
    iso8601 0.1.12 (/home/cefn/.local/lib/python3.6/site-packages)
Uninstall (y/N)?y
Traceback (most recent call last):
  File "/home/cefn/.local/bin/pip-autoremove", line 11, in <module>
    sys.exit(main())
  File "/home/cefn/.local/lib/python3.6/site-packages/pip_autoremove.py", line 106, in main
    autoremove(args, yes=opts.yes)
  File "/home/cefn/.local/lib/python3.6/site-packages/pip_autoremove.py", line 24, in autoremove
    remove_dist(d)
  File "/home/cefn/.local/lib/python3.6/site-packages/pip_autoremove.py", line 83, in remove_dist
    subprocess.check_call(["pip", "uninstall", "-y", dist.project_name])
  File "/usr/lib/python3.6/subprocess.py", line 286, in check_call
    retcode = call(*popenargs, **kwargs)
  File "/usr/lib/python3.6/subprocess.py", line 267, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.6/subprocess.py", line 709, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.6/subprocess.py", line 1344, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'pip': 'pip'

If it actually does have python3 support, but is assuming that pip3 is aliased to pip, this is not always the case, as in my Ubuntu, Debian-based OS which only has pip3 installed and in any case pip would alias to the python2 version.

[im-n1]

+1

[cefn]

Isn't there a way to directly call pip from within the VM anyway which eliminates the need to drop into the system shell? On my machine, (virtualenv with pip3) the following would work.

from pip.__main__ import _main as pipMain
pipMain(["uninstall", "-y", dist.project_name])

[ghost]

Just tried it and it works for me (Python 3.6)

[prof7bit]

It probably only works when pip is a symlink to pip3 but usually (Debian, Ubuntu) these two are completely separate, pip only works with pytrhon2 and pip3 only with python3

[konomikitten]

It would be nice if pip-autoremove produced both pip-autoremove2 and pip-autoremove3 respectively.

[dandrei]

Thanks to @prof7bit's comment I got it working this way:

sudo ln -s /usr/bin/pip3 /usr/bin/pip

[im-n1]

Well there is a pull request #22 which is 3 months old already and no response.

Semms like this project is abandoned ..... at least for now.

[tresni]

tresni/pip-autoremove has been updated to work with python 3.7 and includes most of the PRs from here.

[im-n1]

Looks cool but Poetry..

[tresni]

I’m confused. Are you asking for Poetry support? My fork has the same requirements as this repo (a working python and tox if you want to run tests.)

If you are saying there are other ways to deal with this issue like Poetry or virtualenv or venga, I agree. I still find this tool useful from time to time.

[amard33p]

tresni/pip-autoremove has been updated to work with python 3.7 and includes most of the PRs from here.

This works well with Python 3.7. Just FYI, here's how to install:
pip3 install git+https://github.com/tresni/pip-autoremove.git

[tresni]

Should be addressed by the merge of #42 and the new release, please close if that resolves your issue.

[cefn]

Thanks for your efforts, tresni. I don't have the means of easily testing the original configuration, where pip was aliased to pip2 on debian. These days my pip is aliased to pip3 anyway.

[cefn]

Thanks for your efforts, tresni. I don't have the means of easily testing the original configuration, where pip was aliased to pip2 on debian. These days my pip is aliased to pip3 anyway.