This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Rudd-O
Recipients Rudd-O, tarek
Date 2009-03-14.08:50:46
SpamBayes Score 2.8062414e-10
Marked as misclassified No
Message-id <1237020649.17.0.42577974521.issue5482@psf.upfronthosting.co.za>
In-reply-to
Content
apparently, /usr/lib/python2.4/site-packages IS in the sys.path, which
would seem to indicate that python would actually load pure python
modules from there.

Which means that the only fixes that need to go within distutils would be:

1. a fix so in 64bit arches, pure python modules are STILL INSTALLED
within the /usr/lib/python2.X dir instead of lib64
2. making every RPM built out of a pure python module depend on the
specific Python interpreter it was built under, to a precision of
major.minor version.

Right?

This sort of busts my plan of providing universal RPM packages for all
distributions, BUT... BUT... at least means that a single package can
work in all platforms of all distributions that have a particular
version of the interpreter it was built in.  Which is a space / busywork
savings of at least platforms*distributions.
History
Date User Action Args
2009-03-14 08:50:49Rudd-Osetrecipients: + Rudd-O, tarek
2009-03-14 08:50:49Rudd-Osetmessageid: <1237020649.17.0.42577974521.issue5482@psf.upfronthosting.co.za>
2009-03-14 08:50:47Rudd-Olinkissue5482 messages
2009-03-14 08:50:46Rudd-Ocreate