On Wed, Dec 9, 2009 at 10:52, Guido van Rossum
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. -Brett
?
On Wed, Dec 9, 2009 at 10:48 AM, Brett Cannon
wrote: 2009/12/9 Paul Moore
2009/12/9 Brett Cannon
: I prefer the former as well (don't read any bytecode no matter if
source
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 to turn off bytecode usage; the default behavior is not going to change. -Brett _______________________________________________ Python-ideas mailing list Python-ideas@python.org http://mail.python.org/mailman/listinfo/python-ideas
-- --Guido van Rossum (python.org/~guido)