Skip to content
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

pip install/upgrade --save #3884

Closed
westurner opened this issue Jul 31, 2016 · 4 comments
Closed

pip install/upgrade --save #3884

westurner opened this issue Jul 31, 2016 · 4 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@westurner
Copy link

westurner commented Jul 31, 2016

Description:

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

This feature request is from the distutils mailing list:

@westurner
Copy link
Author

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

@westurner
Copy link
Author

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):

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

pip-tools probably has InstallRequirement.to_requirements_str()?

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
Copy link
Member

Looks like a duplicate of #1479

@westurner
Copy link
Author

On Jul 31, 2016 3:17 PM, "Xavier Fernandez" notifications@github.com
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.

@dstufft dstufft closed this as completed Sep 7, 2016
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 4, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

3 participants