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 ncoghlan
Recipients eric.snow, josh.r, lemburg, ncoghlan, pitrou, pmoody, python-dev, r.david.murray, rhettinger, sbromberger, serhiy.storchaka
Date 2015-03-08.11:25:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425813926.73.0.99804968603.issue23103@psf.upfronthosting.co.za>
In-reply-to
Content
For the record, I don't think the weakref support is likely to be particularly useful either, and if we'd used __slots__ from the beginning, I expect we would have left it out.

It's specifically the idea of *taking weakref support away* when weakrefs currently work that seems dubious to me.

It may be worth asking the question on Python dev, as it's possible I'm being overly cautious, and it would be reasonable to drop the weakref support in 3.5.0, while mentioning in the 3.5 porting notes that we'd be open to the idea of adding weakref support back in a 3.5.x maintenance release if anyone reports its removal as a regression from 3.4.
History
Date User Action Args
2015-03-08 11:25:26ncoghlansetrecipients: + ncoghlan, lemburg, rhettinger, pitrou, pmoody, r.david.murray, python-dev, eric.snow, serhiy.storchaka, josh.r, sbromberger
2015-03-08 11:25:26ncoghlansetmessageid: <1425813926.73.0.99804968603.issue23103@psf.upfronthosting.co.za>
2015-03-08 11:25:26ncoghlanlinkissue23103 messages
2015-03-08 11:25:26ncoghlancreate