URL requirement in argcmdr setup.py prescribes its installation by source URL

[jesteria]

Summary

As a user who would like to take advantage of the resolution of #23 – and really of tomerfiliba/plumbum#604 – I must install argcmdr from its source URL (this repository) rather than from PyPI.

In depth

The current state of pip and setup.py appears to be such that specification of a fork repository requirement –

install_requires=[
    …
    'plumbum @ git+https://github.com/jesteria/plumbum.git@v1.7.2-604',
]

– is interpreted as simply pip install plumbum (from PyPI) unless the setup.py is actually invoked, i.e. unless pip is made to retrieve the source, either:

• pip install https://github.com/dssg/argcmdr/archive/0.12.0.zip
• or in another setup.py: argcmdr @ https://github.com/dssg/argcmdr/archive/0.12.0.zip
  • (…and onwards)

This is exceptional.

Outlook

• The plumbum fork is not desirable, anyway. If made StdinDataRedirection compatible with modifiers writing to stdout tomerfiliba/plumbum#605 is merged, argcmdr's setup.py can go back to a standard requirement.
• If no other packaging solution exists, argcmdr can publish its fork of plumbum – either vendored or on PyPI.
• argcmdr can monkey-patch plumbum with the fix 👎