[issue12998] Memory leak with CTypes Structure
Sebastian Wiesner 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 there is never a need to create the same Structure type twice. Thus the set of Structure subclasses created during the live-time of a program is both, fixed and small, so there is no need to limit the cache size. -- nosy: +lunar ___ Python tracker <http://bugs.python.org/issue12998> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12873] 2to3 incorrectly handles multi-line imports from __future__
Changes by Sebastian Wiesner : -- nosy: +lunar ___ Python tracker <http://bugs.python.org/issue12873> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12873] 2to3 incorrectly handles multi-line imports from __future__
Sebastian Wiesner 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 that this is due to the multi-line future import in "test1.py" because the line-break in the import statement is the only difference between both files. -- ___ Python tracker <http://bugs.python.org/issue12873> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4411] __mro__ documentation
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=__mro__&check_keywords=yes&area=default) Imho __mro__ lacks documentation in "Standard Type Hierachy", where special attributes of fundamental data types are documented. -- assignee: georg.brandl components: Documentation messages: 76355 nosy: georg.brandl, lunar severity: normal status: open title: __mro__ documentation versions: Python 2.7 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4411> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
