Open GoogleCodeExporter opened 8 years ago
I have a suspicion: The characters
{{{
#!/usr/bin/env #!/usr/bin/env
/tmp/fake-home-ci/jobs/workspace/nose-unstable-multi/TOXENV/py25/label/nose-unst
able/.tox/jython_nodeps/bin/jyth
}}}
are of length 128. Seems like we are hitting a linux limitation: search for
"127" in http://homepages.cwi.nl/~aeb/std/shebang/
Hudson tends to produce very long file system paths especially with
multi-config projects. This has hit me before (on windows i think). We could
think about setting TOXDIR (the base dir in which all the envs/logs etc. are
created) to somewhere more directly in the global tempdir. We then might get a
dangling garbage problem (killing the hudson workspace will not remove the
global tmpfiles - and killing them always would remove the caching effect and
makes debugging a failing job harder).
Or we could make tox issue a warning (on linux) if the path to a venv-bin dir
is >=120 or so.
is there any (simple) solution you can think of?
Original comment by holger.k...@gmail.com
on 20 Sep 2010 at 8:14
Ah, I see. What if tox simply managed the $PATH variable then set the shebang
to the executable?
i.e.
PATH=/tmp/fake-home-ci/jobs/workspace/nose-unstable-multi/TOXENV/py25/label/nose
-unstable/.tox/jython_nodeps/bin:${PATH}
#!/usr/bin/env jython
Otherwise, yeah, I think issuing a warning will at least help people to shorten
names of directories and environment names. That would be an easy fix.
Original comment by kumar.mcmillan
on 20 Sep 2010 at 8:30
managing PATH might work - it's not tox though that creates the shebang. It's
setuptools, distribute or distutils (or all of them - don't ask me atm :).
This solution means tox would need to be careful when it calls (directly or
indirectly) scripts because the she-bang paths to the interpreter would now
depend on the current value of the PATH env variable. Somehow linux accepting
1024 bytes in shebangs sounds a lot more reasonable :)
The solution might work well enough though (and if in doubt we might make it
configurable through a tox.ini option).
Original comment by holger.k...@gmail.com
on 20 Sep 2010 at 8:42
oh, rats, I see. In that case it might best to issue a warning until one of us
thinks of something better.
Original comment by kumar.mcmillan
on 20 Sep 2010 at 8:45
Original issue reported on code.google.com by
kumar.mcmillan
on 19 Sep 2010 at 8:57