At 6:41 PM -0500 10/3/05, Stuart Levy wrote: >I'll bet it's a question of python version number. >The stock bittorrent rpms install their stuff under > /usr/lib/python<version>/site-packages/BitTorrent/... >But <version> is a moving target -- 2.2, 2.3, now FC4 uses python 2.4. >If the system's python version doesn't match the one used by >whoever packaged the bittorrent rpm, the modules get installed in a place >where python doesn't look for them. This is necessary, as the Python language is also a moving target and changes between releases. There's no reason to think a complex Python program will work on a different release without testing (and fixing the bugs). >Is there a better way that the bittorrent packagers could have >done this that doesn't require tying their rpm bundles to >particular Fedora releases? They can make a package that looks for the highest installed (or the default) version of Python, and put their program "there". Provided, of course, that their program has been tested to work on on that version of Python. If they install in a Python that isn't the default, they should make sure that their shellbang has the proper path to Python. There may even be more. >Given that I suppose it's not dependent on bleeding-edge >python features, making bittorrent version X.Y depend on >python 2.Z seems uncomfortably inflexible. Should bittorrent >put its modules in some convenient spot, then use a post-install >script to move them to the site-packages directory for the system's >installed version of python? As long as they know it will work with that version of Python. ____________________________________________________________________ TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' <http://www.georgeanelson.com/>
