Re: RFC: python-base, debconf and py/pyc files
On Fri, 23 Mar 2001, Gregor Hoffleit <[EMAIL PROTECTED]> wrote:
> currently, our Python packages mostly ship .py files and compile them into
> ..pyc files at run time in order to save space in the debs.
>
> There's no reason, though, to keep the .py files on machines that only
> deploy software[1]
Yes there is --- tracebacks look awful without .py's.
Fact is, loading of only .pyc's isn't officially supported by Python.
(the official Guido position is "Python is an open-source language. I'm
not going to waste my time *helping you* not distribute source")
I do think we need somewhere where all the .pyc's are "registered", so when
a new version of Python comes along, it can recompile them, since pycs
are not compatible across versions.
--
"I'll be ex-DPL soon anyway so I'm|LUKE: Is Perl better than Python?
looking for someplace else to grab power."|YODA: No...no... no. Quicker,
-- Wichert Akkerman (on debian-private)| easier, more seductive.
For public key, finger [EMAIL PROTECTED] |http://www.{python,debian,gnu}.org
Re: RFC: python-base, debconf and py/pyc files
On Fri, Mar 23, 2001 at 09:39:07PM +0100, Gregor Hoffleit wrote: > I wonder if I should debconf-ify python-base and add an debconf option that > sets a system-wide policy about how to deal with .py/.pyc files. That could > be one of: > > * install both .py and .pyc files > * install only .pyc files > * install only .py files You forgot about .pyo files. I don't think this is worth doing. If you care about space it would be better to look through the library and remove what you don't need. Perhaps the trimming process would include: find /usr/lib/python2.1 -name '*.py' | xargs rm The .py files comprise 13% of the space used by a Python 2.1b2 install. I don't think the savings are worth the cost (poor tracebacks, more for work Gregor). Neil
Re: RFC: python-base, debconf and py/pyc files
On Sat, 24 Mar 2001, Moshe Zadka wrote: <...> > I do think we need somewhere where all the .pyc's are "registered", "locate .pyc"; or maybe locate .py, .pyc, and .pyo files, then reconcile the three lists. > so when > a new version of Python comes along, it can recompile them, since pycs > are not compatible across versions. Another (mostly redundant) DB of filenames... I hope not. - Bruce
Re: RFC: python-base, debconf and py/pyc files
On Sat, 24 Mar 2001, Bruce Sass <[EMAIL PROTECTED]> wrote:
> > I do think we need somewhere where all the .pyc's are "registered",
>
> "locate .pyc"; or maybe locate .py, .pyc, and .pyo files, then
> reconcile the three lists.
I didn't say the file system isn't a good such place. I just said
we need to agree on one. Whatever is *agreed* (or, to be exact,
mandated by Gregor) is fine with me -- it just has to be well documented
so tools can rely on it.
--
"I'll be ex-DPL soon anyway so I'm|LUKE: Is Perl better than Python?
looking for someplace else to grab power."|YODA: No...no... no. Quicker,
-- Wichert Akkerman (on debian-private)| easier, more seductive.
For public key, finger [EMAIL PROTECTED] |http://www.{python,debian,gnu}.org
