Message 351587 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	vstinner
Recipients	jdemeyer, methane, pablogsal, serhiy.storchaka, vstinner
Date	2019-09-10.07:42:59
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
"f.__doc__ = f" or "f.__module__ = f" don't make any sense. It looks like a bug triggered on purpose. While it's bad, it's not a big deal. The fix (commit 3c452404ae178b742967589a0bb4a5ec768d76e0) is causing way worse issues than the "artificial" memory leak (reference cycle). I wrote PR 15826 to revert the change in Python 3.8. bpo-38006 root issues are not well understood nor fixed yet.

"f.__doc__ = f" or "f.__module__ = f" don't make any sense. It looks like a bug triggered on purpose. While it's bad, it's not a big deal.

The fix (commit 3c452404ae178b742967589a0bb4a5ec768d76e0) is causing way worse issues than the "artificial" memory leak (reference cycle). I wrote PR 15826 to revert the change in Python 3.8. bpo-38006 root issues are not well understood nor fixed yet.

History
Date	User	Action	Args
2019-09-10 07:42:59	vstinner	set	recipients: + vstinner, methane, serhiy.storchaka, jdemeyer, pablogsal
2019-09-10 07:42:59	vstinner	set	messageid: <[email protected]>
2019-09-10 07:42:59	vstinner	link	issue33418 messages
2019-09-10 07:42:59	vstinner	create