Change by yota moteuchi :
--
components: +Interpreter Core -Library (Lib)
___
Python tracker
<https://bugs.python.org/issue46312>
___
___
Python-bugs-list mailin
Change by yota moteuchi :
--
components: +Library (Lib)
___
Python tracker
<https://bugs.python.org/issue46312>
___
___
Python-bugs-list mailing list
Unsub
New submission from yota moteuchi :
This improvement proposal is close to : https://bugs.python.org/issue42956 and
also detailed in
https://stackoverflow.com/questions/13855288/turn-slice-into-range
to iterate over a slice, the recommended method seems to be :
s = slice(5,100,3)
for i in
yota moteuchi added the comment:
one option to could be to create a hardlink_to() method which is
link.hardlink_to(target) and in a few release, deprecate link_to ? :)
--
nosy: +yota moteuchi
___
Python tracker
<https://bugs.python.org/issue39
New submission from yota moteuchi :
While compiling a very recent release of Python (ie. 3.9.0rc2) with a fairly
old release of gcc (ie. debian 6.0.6 gcc 4.4.5) I get the following error :
gcc -pthread -c -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall
-std=c99 -Wextra -Wno
yota moteuchi added the comment:
Well, I would disagree with R. David Murray on this.
literal_eval() is meant to safely parse literal pythons "containers" structures.
{1, 2, 3} is a valid literal set(), why would an empty one not be parse-able as
well. I can not predict, when
