Closed GoogleCodeExporter closed 9 years ago
Hi, sorry for the confusion and thanks for the patch. Some of those files were
outdated though. I added a developer readme here
http://code.google.com/p/python-nose/source/detail?r=2d26612db10dc405527013cb988
0115a560c873f#
The best way to run the tests is with tox
Original comment by kumar.mcmillan
on 25 Apr 2011 at 7:10
Thanks for the guidance.
tox is fully resolving symlinks, which causes problems in my environment.
Is that something I can fix?
It should just be running 'python2.6' and not worrying about the symlinks,
similar to what the test.sh was doing.
Original comment by workitha...@gmail.com
on 25 Apr 2011 at 10:46
I've never seen that as a problem, could you provide an example of how the
symlinks cause problems? Is there an exception?
Without tox you'll need setuptools installed globally or within a virtualenv.
Then type this once:
python2.6 setup.py egg_info
And then you can run selftest:
python2.6 selftest.py
If you can get tox working that would be better since it will allow you to run
in Python 3 using the 2to3 build step.
Original comment by kumar.mcmillan
on 26 Apr 2011 at 3:03
We do some very nonstandard wrapping with a symlink to a binary which calls our
wrapper shell script.
This allows the wrapper to be used without complaint in script headers.
The binary relies on its $0 argument to find the shell script, but tox seems to
be running realpath on the python path before calling it.
I realize that this is specific to our setup, but it works in every other
situation I've encountered till now.
It's extremely unusual (and in this case improper) for a caller to read
symlinks after it's found the command it's looking for.
This is low priority, but I was wondering if there was any way that I could
alter tox or its settings to get this working.
Original comment by workitha...@gmail.com
on 26 Apr 2011 at 3:28
you shouldn't need a custom python binary for use with tox -- it uses
virtualenv to isolate your python environments and this is tried and true
across many OSes and versions.
As for fixing it, you could take a look at the tox source or submit a ticket
over there http://codespeak.net/tox/
Original comment by kumar.mcmillan
on 26 Apr 2011 at 3:53
Original issue reported on code.google.com by
workitha...@gmail.com
on 25 Apr 2011 at 5:10Attachments: