Please include scripts under Tools/scripts/, because there is a lot of stuff needed or being usefully for the work with python. E.g. the Python Library Reference says at `8.12 fcntl...': | You can create the modules yourself with the h2py script, | found in the Tools/scripts/ directory
Wow this is an old one. Arbitrarily chose to deploy the scripts under /usr/share/python2.3/Tools/scripts/*py Does that make sense? I can change it if not...
python 2.3.4-5 will have this fixed.
I've browsed both Debian lists and Python-dev. I think /usr/lib/python2.3/Tools was the eventual consensus. But, I don't know. I'd rather see if another precedent has been set before making a plunge into /usr/share. I'll troll around some other distros to see...
Jeff, thanks for your help. Please move the bug back to ASSIGNED if my choice was not appropriate.
Here's the lowdown: Official Python RPM SPEC (Sean's) puts the files in /usr/lib/pythonX.Y/Tools. Turbo Linux puts the files in /usr/lib/pythonX.Y/Tools. Engarde linux also put them in /usr/lib/pythonX.Y/Tools. Everyone else either does it how Redhat used to or they don't even package anything from Tools altogether. Suse just packages idle in python-idle and dumps the rest. My thoughts: /usr/lib/pythonX.Y/Tools seems to be the precedent python.org is trying to set. Even though most of these will *not* be "import"ed into other Python programs, it may do just as well to make them available here for those that are reading through the documentation. Pynche, modulator, idle are made to install in site-packages and reworked from there. So, what's left is a bunch of random sample programs that people can reference. It might even do well to bring this up on Python-dev again before preceding. But, following blindly, it probably should go into /usr/lib/pythonX.Y/Tools.
Red Hat Linux and Red Hat Powertools are currently no longer supported by Red Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED state for these products. However, we do want to make sure that nothing important slips through the cracks. If, in fact, these issues are not resolved in a current Fedora Core Release (such as Fedora Core 5), please open a new issues stating so. Thanks.