On 12/20/2009 1:48 PM, holger krekel wrote:
> Hi all,
>
> i just committed a change which i'd release together with a bunch
> of other things as py-1.1.2. It makes py.test install as
>
> py.test # if python executable has basename 'python'
> py.test3 # if python executable has version_info>= (3,0)
> py.test2.x # if python executable has basename 'python2.x' (x in
> '4567')
> py.test-jython # if we are running on jython2.5
> py.test-pypy # if we are running on pypy
>
> does this make sense to you, objections? It does for me because
> i can more easily run tests with various interpreters. But
> it means if you run "python2.4 setup.py install" you will no[w]
> get a 'py.test2.4' only, and no 'py.test' proper.
Hi Holger,
I thought it is typical for packages to provide *both* the versions -
i.e, foo.exe and foo-2.6.exe as demonstrated by, for instance, the
easy_install script.
Since third-party packagers such as Enstaller, PyPM[1] may use any
interpreter binary ('python' or 'python2.6' - no guarantee) on their
backend build machines, this change will always create a `py.test`
script when 'python' is used to run setup.py. As a consequence, if the
user installs pylib multiple times via different Python X.Y versions,
there will be an overwrite of the main `py.test` script in the bin/
directory. This is not something that is generally desired (the user
would rather want py.test-X.Y scripts[2]).
If instead pylib installed both `py.test` and `py.test-X.Y` script
regardless of the Python binary being used (as, I believe, currently
done by the setuptools's entry points system), it would work around this
limitation. Besides, I don't see any reason making it work otherwise (as
originally proposed by holger).
-srid
***
[1] PyPM is the package manager from ActiveState; I am the developer of
this project.
[2] of relevance:
http://jessenoller.com/2009/07/19/pep-370-per-user-site-packages-and-environment-stew/
_______________________________________________
py-dev mailing list
py-dev@codespeak.net
http://codespeak.net/mailman/listinfo/py-dev
