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 terry.reedy
Recipients andrea.corbellini, belopolsky, georg.brandl, kristjan.jonsson, pitrou, terry.reedy, warp10, ysj.ray
Date 2010-08-06.19:38:11
SpamBayes Score 0.00017397592
Marked as misclassified No
Message-id <1281123495.72.0.904396253357.issue9417@psf.upfronthosting.co.za>
In-reply-to
Content
Andrea: for the purpose of this tracker, a 'bug' is a discrepancy between doc and behavior. The fact that (new-style) classes have circular references was known when they were introduced in 2.2. That fact is not a bug in the above sense. It is a design tradeoff that works OK for the typical case of classes remaining until the end of a program run. Changing the tradeoff embodied in type() is not likely to be accepted.

That said, an alternate no_cr (no circular reference) metaclass (perhaps a type subclass) that contructed cr-free classes, even at the cost of slower lookup, might be a good addition to the stdlib. Ray's ideas seems to me at least plausible. My first thought on location is in functools.
History
Date User Action Args
2010-08-06 19:38:16terry.reedysetrecipients: + terry.reedy, georg.brandl, belopolsky, pitrou, kristjan.jonsson, andrea.corbellini, ysj.ray, warp10
2010-08-06 19:38:15terry.reedysetmessageid: <1281123495.72.0.904396253357.issue9417@psf.upfronthosting.co.za>
2010-08-06 19:38:11terry.reedylinkissue9417 messages
2010-08-06 19:38:11terry.reedycreate