➜

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 charris44, mdk, ncoghlan, ned.deily, pitrou, serhiy.storchaka, vstinner
Date 2016-12-08.09:47:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwbv_Kb-r2PQh4eHUUibH7v4xyHJUpZLZ8i-Wi3c5wm+Qg@mail.gmail.com>
In-reply-to <1481162075.76.0.341565225814.issue28897@psf.upfronthosting.co.za>
Content 
Charles: "OK, you fixed what broke us before. If I revert our fixes
the problem goes away. So, thanks I guess ;) You can close this."

Cool, happy to read that the issue was fixed :-)

If you missed it, the whole mess were backward compatibility when I
extended the warnings API (only internally currently) to implement a
new feature:
https://docs.python.org/dev/whatsnew/3.6.html#warnings

ResourceWarning are now displayed with a traceback where the object
was allocated when tracemalloc is enabled.
History
Date User Action Args
2016-12-08 09:47:48vstinnersetrecipients: + vstinner, ncoghlan, pitrou, ned.deily, charris44, serhiy.storchaka, mdk
2016-12-08 09:47:48vstinnerlinkissue28897 messages
2016-12-08 09:47:48vstinnercreate