--save flag while installing new packages? about pipfile

[notpushkin]

I think, in fact, that this should be the only option (like in yarn) — Pipfile should always be up-to-date with installed packages. This is only an IMHO, though.

[reillysiemens]

@iamale: I, for one, would not like to see that behavior.

For example, let's say I'm working on a project that has some dependencies. I have an existing Pipfile that is aligned with those dependencies. Now I go ahead and install something like IPython for exploring my environment.

I don't want IPython listed in my dependencies. I don't even want it listed in my development or testing dependencies since I'm the only one using it. It should be perfectly acceptable to have packages installed into your environment that aren't reflected in the Pipfile.

[pradyunsg]

Since #47, this is mostly simpler to implement now. The package can be added pinned to the installed version.

Maybe allow --save to take an argument - the group to add the package into (default, dev etc)?

[kennethreitz]

@iamale that would be too much of a departure from current pip behavior, in my opinion.

[defnull]

Yes please.

Unfortunately, this is only possible if Pipfile (not only Pipfile.lock) uses a parseable standard format and there exists a library that supports lossless editing (i.e. load->edit->save while preserving comments and whitespace). Similar to #8, and this would also solve #9 to some extend.

[kennethreitz]

Pipfiles are to be manually written, not generated.

[kennethreitz]

i will think about it, though. the lockfile being always up-to-date is the important mechanism here.

[kennethreitz]

Pipenv does this.

[brokenthorn]

Pipenv does this.

Let me rephrase that. Use pipenv install <package_name>, not pip install <package_name> for the equivalent of npm install <package_name> (--save is optional now with npm and implied by default).