weakref.proxy behaviour in python 3.0
dickinsm at gmail.com
Sat Aug 21 21:45:25 CEST 2010
On Aug 21, 5:06 pm, Nicholas Cole <nicholas.c... at gmail.com> wrote:
> On Sat, Aug 21, 2010 at 3:31 PM, Mark Dickinson <dicki... at gmail.com> wrote:
> > So my guess is that the change was unintentional.
> > It's probably worth a bug report. Even if the behaviour isn't going
> > to change in either 2.x or 3.x (and it probably isn't), it might be
> > possible to clarify the docs.
> I think the docs should be fixed: it would be good to have a list of
> key examples where the behaviour is different. Although the new
> behaviour is better, it certainly tripped me up badly.
> I'm happy to fill a report out, but since you seem to know much more
> about the internals, I wonder if a bug report written by you would be
> more useful!
Please do log in and add any extra comments you feel appropriate.
More information about the Python-list