holger krekel <hol...@merlinux.eu> writes: > Hi all, > > thanks for all your feedback! Here is a revised proposal: > > - for CPython interpreters: > - always install py.test (so the last install wins) > - additionally install py.test with a version suffix (sys.version_info[:2]) > meaning: py.test2.4 py.test2.5 py.test3.1 etc. > (if enough people prefer a dash before the version info, i'll do a dash > :) > - install the other little py.cleanup/py.lookup/py.svnwcrevert etc. > development tools without version suffix > - for PyPy and Jython: > - install py.test-pypy, py.test-jython > i.e.: no py.test proper and no version numbers (yet) > - don't install the other development tools at all because it's unlikely > users will want them to override the cpython mediated ones, particularly > Jython which has a high startup overhead. > > Additionally i can imagine honoring an environment variable > > PYTEST_INHIBIT_VERSIONINSTALL=... > > which would inhibit the creation of py.test$SUFFIX binaries. > This is useful for people working with virtual environments > or PEP370 which already manages per-interpreter versions. > > Sounds fine?
no. these things should really be handled by distribute (or setuptools/distutils). there is nothing special about the py.test script. just imagine a world where every python package X came with a custom X_INHIBIT_VERSIONINSTALL environment variable. If you really like it that way, try to persuade the distribute guys to implement that feature (probably with a switch in ~/.pydistutils.cfg) regards, - ralf _______________________________________________ py-dev mailing list py-dev@codespeak.net http://codespeak.net/mailman/listinfo/py-dev
