Re: Last rites: dev-python/pipenv and dependencies

On Sat, Mar 28, 2026 at 1:27 PM Michał Górny <[email protected]> wrote:
> # Michał Górny <[email protected]> (2026-03-28)
> # pipenv relies very heavily on vendoring.  Every version bump requires
> # a significant effort to unbundle and patch.  On top of that,
> # the resulting packages pin to narrow dependency versions.  Includes
> # dependencies with no other consumers.
> # Removal on 2026-04-27.  Bug #971660.
> dev-python/click-didyoumean
> dev-python/dparse
> dev-python/pipdeptree
> dev-python/pipenv
> dev-python/plette
> dev-python/pythonfinder

I have a question regarding the planned removal of pipenv and related
packages.

I see that a full de-vendor attempt was already made:
https://github.com/gentoo/gentoo/pull/45214

While the result pins some dependency versions, this situation is not
entirely unusual - a number of packages
in the tree already require narrow dependency ranges. Would it be possible
to reuse this work and maintain the
package via proxy-maintainer instead of removing it entirely? It would be
really sad to see this package removed
while the upstream pipenv developer has expressed willingness to help
maintain it in the Gentoo tree.

Additionally, pipenv’s vendoring seems to be a deliberate upstream design
choice to ensure the tool works independently
of the system Python environment. In this specific case, would it make
sense to reconsider the strict "no bundled libraries"
policy, like Debian did (https://packages.debian.org/sid/all/pipenv/filelist
)?

--
Peter.