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 r.david.murray
Recipients josh.r, ncoghlan, pmoody, r.david.murray, sbromberger, serhiy.storchaka
Date 2014-12-23.19:52:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1419364328.71.0.31432154759.issue23103@psf.upfronthosting.co.za>
In-reply-to
Content
If ipaddress objects are already immutable, it seems to me that having a registry that makes it so there is only one instance per ip value isn't a crazy idea.  I've written such code in other contexts and it's not complicated.  We have caching of identifier strings and "common" integer constants for a reason...this seems a logical extension of that policy in the realm of a specific library data type.

The opposite argument is that it may be better left up to the application that has to handle lots of ips to do the caching according to what it knows to be an optimum pattern.  So consider me +0 on the idea.
History
Date User Action Args
2014-12-23 19:52:08r.david.murraysetrecipients: + r.david.murray, ncoghlan, pmoody, serhiy.storchaka, josh.r, sbromberger
2014-12-23 19:52:08r.david.murraysetmessageid: <1419364328.71.0.31432154759.issue23103@psf.upfronthosting.co.za>
2014-12-23 19:52:08r.david.murraylinkissue23103 messages
2014-12-23 19:52:08r.david.murraycreate