[Python-ideas] disabling .pyc and .pyo files
brett at python.org
Wed Dec 9 19:57:43 CET 2009
On Wed, Dec 9, 2009 at 10:52, Guido van Rossum <guido at python.org> wrote:
> Could it be as simple as this:
> -b don't read bytecode (new flag)
> -B don't write bytecode (existing flag)
Unfortunately no: -b is "issue warnings about str(bytes_instance),
str(bytearray_instance) and comparing bytes/bytearray with str. (-bb: issue
errors)" under python3.
> On Wed, Dec 9, 2009 at 10:48 AM, Brett Cannon <brett at python.org> wrote:
> > 2009/12/9 Paul Moore <p.f.moore at gmail.com>
> >> 2009/12/9 Brett Cannon <brett at python.org>:
> >> > I prefer the former as well (don't read any bytecode no matter if
> >> > is
> >> > available or not); clear and simple semantics that are easy to
> >> > implement.
> >> If that's the rule, what is the point in writing bytecode at all?
> >> It'll never be read...
> > This entire discussion is in the context of having a flag you need to set
> > turn off bytecode usage; the default behavior is not going to change.
> > -Brett
> > _______________________________________________
> > Python-ideas mailing list
> > Python-ideas at python.org
> > http://mail.python.org/mailman/listinfo/python-ideas
> --Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-ideas