requirements file handling with --save option

[jnoortheen]

What's the problem this feature will solve?

It will solve the issue described in #1479

Describe the solution you'd like

• add --save option to install, uninstall commands

I have created a wrapper around pip called pipm. It doesn't depend on anything other than pip and stdlib.
setup.cfg -> as the metafile
requirements.txt -> as the lockfile

Is it possible to add those features pip itself? I just wanted to know before proceeding to create a pull request.

[McSinyx]

Hi there, FYI there's a ongoing development for requirements.txt: Pipfile, which is now currently handled by Pipenv. I don't have any opinion on this particular issue though.

[jnoortheen]

Yes I know about that those things. There has no recent release of pipenv (I think it was on 2018), because of its own set of issues. Poetry seems more robust. Here the change is very little but will make pip as a standalone tool for development, without the need for pip-tools.

[McSinyx]

Pipenv's next release will be in a very near future. I'm not sure what's the vision for pip to be though--I've always been thinking that it is a package manager rather than a collection of common utils for development. I could be wrong though, and it is best for a pip's maintainer to answer this question.

[xavfernandez]

@jnoortheen as you've mentionned yourself this is a duplicate of #1479.
Please keep the discussion in a single issue.

[jnoortheen]

I am asking if I can start creating a PR for this feature. Does pip want to have this by default?

[uranusjr]

1. This question should have been asked in the old issue.
2. I don’t think using setup.cfg is viable since configparser is incapable of doing round-trip read-write. It may work for certain usages, but once you put it in pip users will come asking for “reasonable” features it can never implement. I’m about -0 on the idea in general, but strongly object to this particular proposal.

[jnoortheen]

Is it possible to add those features pip itself? I just wanted to know before proceeding to create a pull request.

1. I did ask in the issue description.

2. OK.