On Sat, Mar 31, 2001 at 01:06:48AM +0200, M.-A. Lemburg wrote:
The reason is simple: the Python API has changed between versions and also the path used by the files inside the packages use the major.minor version number.
The same problem most probably also occurrs for bdist_dumb archives and most other binary distribution formats.
With rpm and probably other package formats like deb, you can have a requires that indicates the version of python needed for installation. E.g. if you place Requires: BeOpen-Python = 2.0 in the spec file, the resulting rpm won't install on systems without python 2.0 user intervention. Similarly a BuildRequires tag allows for specifying dependencies in the build process although I don't think it is very applicable to bdist.
Thanks for the infos. My main certain about the filename is different though: I want people to download the correct version for their system and also need to provide separate files for different Python versions.
-- Marc-Andre Lemburg