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[
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
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 no
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
4 matches
Mail list logo
