On Tue, 13 Jun 2006, martin f krafft wrote: > also sprach Matthias Klose <[EMAIL PROTECTED]> [2006.06.13.0149 +0200]: > > - The current pythonX.Y-foo packages having modules in the python > > library path are collapsed into one package python-foo. Binary > > independent modules are made available for the python versions > > currently supported in the distribution. Binary dependent > > extensions are put for all supported python versions into the > > same python-foo package. The overhead for a maybe unused > > Python will create optimised, binary dependent modules on first > access to .py files, right? In our case, though, this fails because > /usr is mostly read-only to those running Python.
The byte-compilation is done in the postinst (with root rights), so it works. > Couldn't Python be extended to store .pyc files in /var? Python doesn't need to be changed. If you use python-support that's precisely what will happen for public modules (but they are still created in the postint with root rights). Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
