Work around too long shebang lines when installing about dh-virtualenv HOT 6 CLOSED

Can you consider adding another cli option or two to specify virtualenv build dir explicitly or to ask dh_virtualenv to allocate one in /tmp?

from dh-virtualenv.

I'd assume a build system being used could handle that, I'm pretty sure there's a debhelper option to tell where to build. Or were you thinking this as a some other kind of fix?

A side note btw, I'm thinking of closing this issue. Moving things under /opt gave more leverage and I'm quite convinced there's no easy way of solving this issue.

from dh-virtualenv.

I'm talking of a problem arising during package build process, when paths may be getting too lengthy.
The problem, as I can see from the source code, roots in how value of self.package_dir is constructed. It always starts with debian/ folder, which in turn may be well buried in some CI agent working directory.
What if we could ask dh-virtualenv to create a virtualenv elsewhere, say in /tmp directory, which will help us avoid subsequent problems with installing things with pip? After the requirements.txt is processed, of course, we will have to move the virtualenv to its proper subdirectory within debian/ folder right before packaging.

from dh-virtualenv.

Looks like the problem I've encountered (with the very creation of a virtualenv inside a deep folder) shows up in Ubuntu 12.04 but not in 14.04 or newer. Other possible solutions: upgrade python-virtualenv or Ubuntu.

from dh-virtualenv.

See #225

from dh-virtualenv.

I believe this is now fixed by upstream pip and the changes in dh-virtualenv. Let me know if we still need to change behaviour of dh-virtualenv to take these long shebangs into account.

from dh-virtualenv.