[issue14445] Providing more fine-grained control over assert statements

[Irit Katriel]

Irit Katriel  added the comment:

I am closing this because there was no followup for over 9 years. If you are 
still interested in pursuing this, please raise it for discussion on 
python-ideas and open a new issue once there is agreement on how to proceed.

--
nosy: +iritkatriel
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14445] Providing more fine-grained control over assert statements

[Antoine Pitrou]

Antoine Pitrou  added the comment:

This should be discussed on python-dev 
(http://mail.python.org/mailman/listinfo/python-dev) or python-ideas 
(http://mail.python.org/mailman/listinfo/python-ideas).

--
nosy: +pitrou

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue14445] Providing more fine-grained control over assert statements

[Max]

New submission from Max :

Currently -O optimizer flag disables assert statements.

I want to ask that more fine-grained control is offered to users over the 
assert statements. In many cases, it would be nice to have the option of 
keeping asserts in release code, while still performing optimizations (if any 
are offered in the future). It can be achieved by removing the "disable 
assertions" feature of the -O flag, and instead adding a new flag that does 
nothing but disables asserts.

--
messages: 157070
nosy: max
priority: normal
severity: normal
status: open
title: Providing more fine-grained control over assert statements
type: enhancement
versions: Python 3.4

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com