Dh virtualenv test #91
Conversation
sopelj
force-pushed
the
dh-virtualenv-test
branch
2 times, most recently
from
368c0dc
to
679c3c0
Compare
|
Build succeeded. ✔️ tox-linters SUCCESS in 4m 59s |
|
Build succeeded. ✔️ tox-linters SUCCESS in 3m 43s |
sopelj
force-pushed
the
dh-virtualenv-test
branch
from
9e483b2
to
33ab057
Compare
|
Build succeeded. ✔️ tox-linters SUCCESS in 3m 45s |
|
This is sort of a proof of concept, and should be tested a bit more before merging. However, it does build and install correctly and seems to work perfectly fine. The versions could also be bumped if desired, but for now it is essentially the same as before, but the package contains its own versions of its dependencies instead of using system ones. And thus they should be updated to maintained versions and not rely on Debian's. |
|
Have you tried with a plugin, is there is any impact to register an entrypoint from an external program with this changes? |
That's a good question! I have not tried with an external program. Do you have any examples we could test with? If it is installed system-wide it would probably not be detected as the default option is to not include system packages. If it's something installed by a third party they could simply install it into the virtualenv for this service. If it's something we package, we might have to look into how sharing a virtualenv might work or changing path settings for package discovery. |
No description provided.