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 rhettinger
Recipients Antony.Lee, pitrou, rhettinger
Date 2017-08-24.18:01:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1503597662.11.0.36358839416.issue31254@psf.upfronthosting.co.za>
In-reply-to
Content
We should still ask about use cases though.  Without a motivating use case, why churn the code, complexify the API (possibly making it more tricky to use), and risk introducing bugs?

AFAICT, the OP's sole motivation was "still, it would seem preferable ..." which is no more compelling than the usual "it might be nice if ...".  

The weak reference containers have been around for a long time and I don't think anyone has ever reported that they actually needed this functionality.
History
Date User Action Args
2017-08-24 18:01:02rhettingersetrecipients: + rhettinger, pitrou, Antony.Lee
2017-08-24 18:01:02rhettingersetmessageid: <1503597662.11.0.36358839416.issue31254@psf.upfronthosting.co.za>
2017-08-24 18:01:02rhettingerlinkissue31254 messages
2017-08-24 18:01:01rhettingercreate