A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2013-November/130272.html below:

[Python-Dev] (#19562) Asserts in Python stdlib code (datetime.py)

[Python-Dev] (#19562) Asserts in Python stdlib code (datetime.py)Maciej Fijalkowski fijall at gmail.com
Sat Nov 16 16:34:15 CET 2013
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)
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4