This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author petr.viktorin
Recipients petr.viktorin, shihai1991, vstinner
Date 2020-11-03.22:26:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1604442360.35.0.0941904332471.issue41618@roundup.psfhosted.org>
In-reply-to
Content
> Can we write those info to docs? In case some developer want to exposing slot in future.

Do you mean something like "only expose a slot if you have a reason for exposing it"? That sounds like a tautology.
Where in the docs would this go?

> nb_inserved in PyNumberMethods should be removed?

You mean nb_reserved, right?
It can't be removed; old-style initialization is positional.
But it could be replaced according to PEP387:
- in 3.x, raise a warning if it is not set to NULL (in static types)
- in 3.x+2, throw an error if it is not set to NULL (in static types)
- in 3.x+3 or later, it can be replaced by another slot, if there's something we need to add to PyNumberMethods
History
Date User Action Args
2020-11-03 22:26:00petr.viktorinsetrecipients: + petr.viktorin, vstinner, shihai1991
2020-11-03 22:26:00petr.viktorinsetmessageid: <1604442360.35.0.0941904332471.issue41618@roundup.psfhosted.org>
2020-11-03 22:26:00petr.viktorinlinkissue41618 messages
2020-11-03 22:26:00petr.viktorincreate