Hi, Anark Karabey <k4r4...@riseup.net> writes:
> Package: elpa-pyvenv > Version: 1.21+git20201124.37e7cb1-1 > Severity: normal > X-Debbugs-Cc: none, <user@host.localdomain> > > Dear Maintainer, > > Elpa-pyvenv package shouldn't hard depend on virtualenv package, which > also pulls-in python3-virtualenv package. The latter package "seems to > be" (to my novice eye, please correct me if I am wrong) mostly > superseded by python3-venv package, which is python3's "built-in" way of > creating and managing virtualenvs. > > If elpa-pyvenv drops its hard dependance on virtualenv, my debian system > will be freed of following two packages: > > - virtualenv > - python3-virtualenv > > since, I already have python3-venv installed. > > Here's a message from elpa-pyvenv's github issue thread that signals it > shoudln't "hard depend" on virtualenv, and that it should already work > with virtual environments that are created using python3-venv: > https://github.com/jorgenschaefer/pyvenv/issues/58 > I think this is a good suggestion. A simple fix is to add python3-venv as an alternative to virtualenv. Also, I wonder whether it provides more flexibility to downgrade these from hard depends to recommends, so that elpa-pyvenv is also usable with virtual environment created by an externally installed Python. Suggestions welcome. > [...] -- Regards, Xiyue Deng
signature.asc
Description: PGP signature
