I don't want to recommend atexit or weakref because they have their pitfall.
I think the context manager should be considered at first when people want
to use __del__.
On Wed, Jan 1, 2020 at 9:35 AM Yonatan Zunger wrote:
>
> Hey everyone,
>
> I just encountered yet another reason to beware of
Jeff, I like all of your proposals. It does get a bit long, but I think
it's not so long that it feels out-of-place in the data model docs, which
is where you expect weird stuff to live. (I mean, look how long the
discussion of metaclasses is -- and I certainly wouldn't want to eliminate
that!)
ACTIVITY SUMMARY (2019-12-27 - 2020-01-03)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open7227 (+24)
closed 43726 (+38)
total 50953 (+62)
Open issues
On 2019-11-25 13:15, Stefan Behnel wrote:
Hi all,
I think that PEP 573 is ready to be accepted, to greatly improve the state
of extension modules in CPython 3.9.
https://www.python.org/dev/peps/pep-0573/
It has come a long way since the original proposal and went through several
iterations
On 2019-12-26 14:35, Michael wrote:
First - best wishes all for a happy and healthy 2020!
As my nickname implies - my primary means to contribute to Python is
with regard to AIX. One of the things I recently came across is
Misc/README.AIX which was last updated sometime between 2010 and 2014. I
On 02/01/2020 02:53, Yonatan Zunger wrote:
Oh, I'm absolutely thinking about clarity. ...
Could any revision also be clear what is *required of Python the
language* vs. what is a CPython implementation detail? I always
appreciate this care. There is good practice here and elsewhere in the
Could there be a clearer separation between the language semantics and
current CPython behavior?
On 2020-01-02 03:53, Yonatan Zunger wrote:
Oh, I'm absolutely thinking about clarity. Something like:
This method is called when the instance is about to be destroyed.
Because it may be
