I think it's far-fetched to start thinking pip is legacy. Pipfile has had a goal from day 1 to be a format that pip would support. PEP 582 is a path forward here for providing a default location for a virtualenv [2] - it's just that everything moves slower in pip because it supports more use-cases than a tool like pipenv. What started out as a reference implementation has definitely taken on a life of its own of course and it's up to PyPA to manage that relationship and offer a good story around the tooling it's building.

[1] https://github.com/pypa/pipfile#pip-integration-eventual
[2] https://www.python.org/dev/peps/pep-0582/

On Thu, Sep 20, 2018 at 1:38 PM Bert JW Regeer <xistence@0x58.com> wrote:


On Sep 20, 2018, at 12:11, Tzu-ping Chung <uranusjr@gmail.com> wrote:


On 21 Sep 2018, at 02:01, Bert JW Regeer <xistence@0x58.com> wrote:



On Sep 19, 2018, at 23:22, Chris Jerdonek <chris.jerdonek@gmail.com> wrote:

Thus, it's looking like things could be on track to split the user and maintainer base in two, with pip bearing the legacy burden and perhaps not seeing the improvements. Are we okay with that future?

This'll be a sad day. pip is still used as an installer by other build system where using pipenv is simply not a possibility.

I am not quite sure I understand why you’d think so. pip has been bearing the legacy burden for years, and if this is the future (not saying it is), it would more like just another day in the office for pip users, since nothing is changing.

pip not seeing any improvements is something I think will be sad. I don't use pipenv, but use poetry which uses pip behind the scenes to do installation. I also use flit. For either of those cases I would think it sad that pipenv splits from pip, and then developers of alternate tooling around building packages (but not installing) don't get new improvements because "pip is legacy".

pipenv doesn't work in various scenarios, and trying to shoehorn it into those scenarios is just wrong especially since it wasn't designed to do those things.
--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-leave@python.org
https://mail.python.org/mm3/mailman3/lists/distutils-sig.python.org/
Message archived at https://mail.python.org/mm3/archives/list/distutils-sig@python.org/message/3JKW3DJYVAGENQNQRLEAKKJXQC2QXIZF/