© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
688b375
demo site
(Get the code!)
From *Deviations_
https:/
-----------
* dist-packages instead of site-packages. Third party Python software installed from Debian packages goes into dist-packages, not site-packages. This is to reduce conflict between the system Python, and any from-source Python build you might install manually.
-----------
A more detailed discussion on the same issue can be found here in Debian's bug tracker:
https:/
That says Debian deliberately treat .deb python packages and manually installed python modules differently. They changed the stock Debian Pythons' module path from `site-packages` to `dist-packages`. So the stock Python uses modules only from DEB sources (installs to `dist-packages`) and not from easy_install or otherwise compiled (installs to `site-packages`).
Automake either doesn't care or horner the management ideal. They only support you to install your python library into `site-packages` so it doesn't overwrite the packages you installed with .deb.
If Automake provide config directive to override `pyexecdir` and `pythondir`, it would be a much better tool for system package developers (e.g. Python based ibus engine developer) for proper testing. I found no such option yet.