Jyrki Pulliainen

Thanks for reporting the issue. First off, not working across Python versions is universally a known thing with virtualenv, not specific for a dh-virtualenv. This could of course be documented...

Ah, sorry for misunderstanding! I do agree and indeed the substvars would solve this issue. There is already some logic due to changes on Debian to record the major python...

Thanks for the report! I don’t follow launchpad bugs, since primarily I only publish this to Debian unstable. But thanks for the report anyhow, does not hurt with extra visibility...

Ha, not a bad idea either :)

Whoa, cool! I'll leave this ticket open so I remember to reference this in the documentation. Thanks a lot once again @jhermann :)

Maybe we can make readme a tad more vague on details and point to the doc? Fully agree on reducing duplication

I agree here that there is no need for a specific new option for this. On Sun, 30 Apr 2017 at 16:31, Jürgen Hermann wrote: > --preinstall "setuptools>=17.1" (or another...

Hi! Thanks for the bug report. Feels definitely something we should work on. I wonder what is the general opinion on how to handle this: We could default on some...

I think there is a change with compatibility level 12, which needs a change with dh-virtualenv. For immediate fix you could try building with compat 11? On Sat 24. Apr...

`dh-virtualenv` already depends on `virtualenv | python-virtualenv (>= 1.7) | python3-venv`, which covers the `python3-venv`. In any case an additional package is required, wether it is `virtualenv` or `python3-venv`. Now,...