On Aug 21, 5:06 pm, Nicholas Cole wrote:
> On Sat, Aug 21, 2010 at 3:31 PM, Mark Dickinson wrote:
>
> [SNIP]
>
> > 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
On Sat, Aug 21, 2010 at 3:31 PM, Mark Dickinson wrote:
[SNIP]
> 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.
Dear M
On Aug 21, 1:13 pm, Nicholas Cole wrote:
> I've searched for information on this without success. Has
> weakref.proxy changed in Python 3? I couldn't see any note in the
> documentation, but the following code behaves differently on Python
> 2.6.1 and Python 3:
>
> import weakref
> class Test(ob
Dear List,
I've searched for information on this without success. Has
weakref.proxy changed in Python 3? I couldn't see any note in the
documentation, but the following code behaves differently on Python
2.6.1 and Python 3:
import weakref
class Test(object): pass
realobject = Test()
pobject =
