On: Generate pip requirements.txt file based on imports of any project

[remram]

I had forgotten about pipfiles. Like their name implies (/s) they are not for pip but pipenv, a separate tool.

https://github.com/pypa/pipfile "This format is still under active design and development", last commit "2 years ago". I think this is dead.

[999900000999 → remram]

https://github.com/pypa/pipenv

Pipenv was last updated 10 hours ago. Looks like it's still an active project to me.

[kstrauser → remram]

That's the repo for the Pipfiles themselves. The (only?) thing using them is pipenv, which lives in a separate repo.

[remram → kstrauser]

Pipfiles is what we are talking about.

[kstrauser → remram]

True, but Pipfiles are basically whatever pipenv wants them to be. I'm not aware of anything but pipenv that uses them, although I'm sure there are more than zero such things. My point here being that I wouldn't take a lack of commits to the Pipfiles repo to mean that they're not still under development. More likely it's just being developed in the pipenv repo.

But in any case, I'd vastly prefer the standard pyproject.toml over some file specific to mostly one tool.

[remram → kstrauser]

The pipfile repo claims the opposite:

> This repository contains the design specification of the Pipfile format, as well as a proposed implementation of a parser for the specification which can be used by Pipenv and, in the future, any other consumer (e.g. pip)

It should probably be updated to reflect whatever the current status and goals are.