[Python-Dev] (#19562) Asserts in Python stdlib code (datetime.py) (original) (raw)
Maciej Fijalkowski fijall at gmail.com
Sat Nov 16 16:34:15 CET 2013
- Previous message: [Python-Dev] (#19562) Asserts in Python stdlib code (datetime.py)
- Next message: [Python-Dev] (#19562) Asserts in Python stdlib code (datetime.py)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Nov 16, 2013 at 5:33 PM, Maciej Fijalkowski <fijall at gmail.com> wrote:
On Sat, Nov 16, 2013 at 5:09 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
On 16 November 2013 23:17, Maciej Fijalkowski <fijall at gmail.com> wrote:
On Sat, Nov 16, 2013 at 3:51 AM, Terry Reedy <tjreedy at udel.edu> wrote:
If user input can trigger an assert, then the code should raise a normal exception that will not disappear with -OO.
May I assert that -OO should instead be killed? "I don't care about embedded devices" is not a good rationale for killing features that really only benefit people running Python on such systems. Cheers, Nick. Can I see some writeup how -OO benefit embedded devices?
Or more importantly, how removing assert does. And how not naming it --remove-asserts would not help (people really have an opinion it would optimize their code)
- Previous message: [Python-Dev] (#19562) Asserts in Python stdlib code (datetime.py)
- Next message: [Python-Dev] (#19562) Asserts in Python stdlib code (datetime.py)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]