A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] [Python-checkins] Daily reference leaks (d7e490db8d54): sum=61494 [Python-Dev] [Python-checkins] Daily reference leaks (d7e490db8d54): sum=61494Ethan Furman ethan at stoneleaf.us
Wed Oct 21 13:10:56 EDT 2015
On 10/21/2015 08:53 AM, Random832 wrote:

> 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?

Where can I find out more about using `object.__new__` as a decorator?

--
~Ethan~

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4