[ python-Bugs-862600 ] Assignment to __builtins__.__debug__ doesn't
do anything.
SourceForge.net
noreply at sourceforge.net
Thu Dec 18 18:55:52 EST 2003
Bugs item #862600, was opened at 2003-12-18 18:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=862600&group_id=5470
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Jeremy Fincher (jemfinch)
Assigned to: Nobody/Anonymous (nobody)
Summary: Assignment to __builtins__.__debug__ doesn't do anything.
Initial Comment:
In 2.2, it would dynamically turn off asserts:
Python 2.2.3+ (#1, Sep 30 2003, 01:19:08)
[GCC 3.3.2 20030908 (Debian prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more
information.
>>> __debug__
1
>>> __builtins__.__debug__ = 0
>>> assert 0, "There should be nothing raised."
>>>
But in 2.3, this changed:
Python 2.3.2 (#2, Nov 11 2003, 00:22:57)
[GCC 3.3.2 (Debian)] on linux2
Type "help", "copyright", "credits" or "license" for more
information.
>>> __debug__
True
>>> __builtins__debug__ = False
>>> assert 0, "There should be nothing raised."
Traceback (most recent call last):
File "<stdin>", line 1, in ?
AssertionError: There should be nothing raised.
>>>
If this is in fact the intended behavior (I hope it's not) then
what's an application author to do when he wants to offer
users a -O option *to his application* that turns off asserts?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=862600&group_id=5470
More information about the Python-bugs-list
mailing list