(original) (raw)

Sorry about introducing this. Where can I subscribe to these automated
emails.

Also, how do I go about running this locally?

On default I tried running
\`./python -m test -l test\_capi\` did not print anything about leaks. I think that
using \`object.\_\_new\_\_\` as a decorator here is the same as subclassing object,
overriding \_\_new\_\_ and then making a call to \`super().\_\_new\_\_\` so I would
imagine this bug could appear in less "clever" situations. I would love to help
fix this issue; Benjamin, you mentioned that you think that maybe all heaptypes
should have gc, do you have a suggestion on where I can look in the code to try
to make this change?

On Wed, Oct 21, 2015 at 11:53 AM, Random832 <random832@fastmail.com> wrote:

Raymond Hettinger <raymond.hettinger@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?

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev

Unsubscribe: https://mail.python.org/mailman/options/python-dev/joe%40quantopian.com

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org