Archive pypa/pipenv

[Pomax]

As a project that is no longer maintained, please have the pypa/pipenv project owner(s) archive the repo on github (and pypi if possible) so that people can start planning their migrations to newer, maintained solutions, and new projects don't reach for an unmaintained solution anymore. Archiving will still leave the code fully accessible, and will not affect any existing direct dependencies based on github url.

If possible, also please respond on pypa/pipenv#4058 so that the community doesn't have to keep guessing at whether anyone should still be using pipenv (especially as all signs point to that they shouldn't).

[benatkin]

Archiving isn't a very nice feature. There's a reason github took so long to implement it. I think it would be nice to move out of the pypa GitHub organization so it's on equal footing with Poetry and other alternatives, though.

[Pomax]

Also fine; the main concern is to have a clear indication about whether it's still maintained or should be considered a legacy solution. I see Dan responded on the linked issue about its activity status, so If moving it out of the pypa org is an option, then that'd be an excellent thing to do at the same time as Dan works on the pipenv repo itself.

[pganssle]

A maintainer has already commented on that thread. We will not be archiving pipenv unless the maintainers of that project want that.

Please direct further comments to pypa/pipenv#4058.