Sebastian Wiesner lunary...@googlemail.com added the comment:
Why should it? After all, you're sort of abusing ctypes by repeatedly creating
Struture types over and over again. C structures that you might want to wrap
with these types are fixed and known at the time of programming, so
Sebastian Wiesner lunary...@googlemail.com added the comment:
More precisely, the bug is, that 2to3 refactors the print() invocation in
test1.py though it shouldn't because a print_function future import is
present at the beginning of test1.py. The cross-check with test2.py shows
Changes by Sebastian Wiesner lunary...@googlemail.com:
--
nosy: +lunar
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12873
___
___
Python-bugs
New submission from Sebastian Wiesner [EMAIL PROTECTED]:
The documentation of Python 2.6 and 2.7 only mentions the class
attribute __mro__ in ABC documentation and in Data model documentation
when explaining description invocation (see search results:
http://docs.python.org/dev/search.html?q
