pip install/upgrade --save

[westurner]

Description:

When installing or upgrading, the option to --save to the given requirements.txt

This feature request is from the distutils mailing list:

• [Distutils] Proposal: "Install and save"
  https://www.mail-archive.com/[email protected]/msg24809.html

[westurner]

So, to clarify, the need here is to add to or update requirements files from the CLI when --save is specified:

• https://pip.pypa.io/en/latest/user_guide/#requirements-files
• https://pip.pypa.io/en/latest/reference/pip_install/#requirements-file-format

[westurner]

pipup has "save to a requirements.txt" functionality
https://github.com/revsys/pipup

It looks like it doesn't yet handle hash-checking mode (which is from peep, IIRC):

• https://pip.pypa.io/en/stable/reference/pip_install/#hash-checking-mode
• https://github.com/revsys/pipup/blob/master/pipup/req_files.py

I think str(req_install.InstallRequirement) could/should just work? Or maybe to_requirements_str()?

• https://github.com/pypa/pip/blob/master/pip/req/req_file.py
• https://github.com/pypa/pip/blob/master/pip/req/req_install.py

pip-tools probably has InstallRequirement.to_requirements_str()?

• https://github.com/nvie/pip-tools/blob/master/piptools/writer.py
• https://github.com/nvie/pip-tools/blob/master/piptools/utils.py
• format_requirement()
• format_specifier()

Round-trip with requirements.txt files would probably be useful

InstallRequirement.to_requirements_str()

• this could just be str(InstallRequirement()), but the current implementation does not preserve the whole InstallRequirement
• this must preserve the whole line, changing only the version specifier and the --hash option

Usage:

• pip install --save pkg
• pip install --upgrade pkg

Questions:

• Should --save include a `--hash= by default``?

[xavfernandez]

Looks like a duplicate of #1479

[westurner]

On Jul 31, 2016 3:17 PM, "Xavier Fernandez" [email protected]
wrote:

Looks like a duplicate of #1479

Thanks!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.