RetroSearch Browse

Wed Oct 21 11:53:45 EDT 2015 · https://mail.python.org/pipermail/python-dev/2015-October/141997.html

Raymond Hettinger <raymond.hettinger at gmail.com> writes:
> Thanks for hunting this down.  I had seen the automated reference leak
> posts but didn't suspect that a pure python class would have caused
> the leak.
>
> I'm re-opening
> https://mail.python.org/pipermail/python-dev/2015-October/141993.html
> and will take a look at it this weekend.  If I don't see an obvious
> fix, I'll revert Joe's patch until a correct patch is supplied and
> reviewed.

If a pure python class can cause a reference leak, doesn't that mean it
is only a symptom rather than the real cause? Or is it that the use of
@object.__new__ is considered "too clever" to be worth fixing?

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-October/141997.html below:

[Python-Dev] [Python-checkins] Daily reference leaks (d7e490db8d54): sum=61494