On Fri, 2005-12-30 at 12:33 -0600, Joe Wreschnig wrote:
> 1. Stop compiling .pyo files, entirely (I'm hoping for little argument
> on this).
>
> Rationale: .pyo files are a joke. They aren't optimized in any
> meaningful sense, they just have asserts removed. Examples for several
> non-trivial fil
On Mon, 2006-01-02 at 18:31 +0100, "Martin v. Löwis" wrote:
> Joe Wreschnig wrote:
> > 1. Stop compiling .pyo files, entirely (I'm hoping for little
> > argument on this).
>
> I agree.
>
> > How?: compileall.py:57, -cfile = fullname +
> > (__debug__ and 'c' or 'o') +
Joe Wreschnig wrote:
> 1. Stop compiling .pyo files, entirely (I'm hoping for little
> argument on this).
I agree.
> How?: compileall.py:57, -cfile = fullname +
> (__debug__ and 'c' or 'o') +cfile = fullname + 'c'
This is the wrong solution, though. If Python is
Le dimanche 01 janvier 2006 à 16:14 -0600, Joe Wreschnig a écrit :
> > The real fix for this issue isn't to stop generating the .pyc files. It
> > is to make python not generate any .pyc files at all when running as
> > root.
>
> Well, I would say, not generate any pyc files unless requested,
> re
On Sun, 2006-01-01 at 19:09 +0100, Josselin Mouette wrote:
> > 2. Stop compiling .pyc files (this I expect to be contentious), unless a
> > package wants to.
> >
> > Rationale: .pyc files have a minimal gain, and numerous failings.
> >
> > Advantages of .pyc files:
> > * .pyc files make Python im
Le vendredi 30 décembre 2005 à 12:33 -0600, Joe Wreschnig a écrit :
> 1. Stop compiling .pyo files, entirely (I'm hoping for little argument
> on this).
>
> Rationale: .pyo files are a joke. They aren't optimized in any
> meaningful sense, they just have asserts removed. Examples for several
> non
On Fri, Dec 30, 2005 at 10:59:45PM -0600, Kenneth Pronovici wrote:
> What would you suggest doing about "hybrid" packages which are primarily
> applications, but also want to make their modules available to other
> Python programs? Two examples here are pychecker and epydoc (both
> maintained by m
On Fri, 2005-12-30 at 22:59 -0600, Kenneth Pronovici wrote:
> > About a month ago Steve Langasek and I discussed the state of Python
> > packages on IRC, in particular the effects of bytecode compilation; the
> > effectiveness (or lack thereof) of it, and how it tightens Python
> > dependencies. I'
> About a month ago Steve Langasek and I discussed the state of Python
> packages on IRC, in particular the effects of bytecode compilation; the
> effectiveness (or lack thereof) of it, and how it tightens Python
> dependencies. I'd like to propose three changes to how Python modules
> are handled.
9 matches
Mail list logo
