Lluís added the comment:
Confirmed with 2.7 as well.
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/issue28571>
___
___
Python-bugs-list m
New submission from Lluís:
I'm running this small script that produces a segfault:
https://gist.github.com/anonymous/d24748d5b6de88b31f18965932744211
My python version is Python 3.5.2 (default, Jun 28 2016, 08:46:01) [GCC 6.1.1
20160602] on linux. And running scipy version 0.18.1.
New submission from Lluís:
The following code works without raising any AssertionError
>>> n = "some small integer value"
>>> m = "some larger integer value"
>>> assert n>> data = bytearray(n)
>>> mem = memoryview(data)
>>&
Lluís added the comment:
Thanks for the explanation, I didn't know of the exact behavior of __debug__.
I close ticket.
--
resolution: -> works for me
status: open -> closed
___
Python tracker
<http://bugs.python.
Lluís added the comment:
David, the problem is that if you have the logging inside a loop, the
interpreter will have to evaluate the condition every time. With an assert you
guarantee that *no code* is executed.
I know that we can find thousands of ways to do that, even writing a dynamic
Lluís added the comment:
storchaka, you're right, but since non of the debug(), info() etc. functions
have a return value, it would cause no trouble and would be neater to add a
"return True". I'm not sure, but probably
New submission from Lluís :
One of the problems with the logging library is that it can affect code
performance when logging calls are over-utilized.
One possible solution would be to allow the compiler to remove logging calls
when code is optimized with "python -O" by wrapping log
