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 vstinner
Recipients arhadthedev, erlendaasland, gdr@garethrees.org, lemburg, mark.dickinson, rhettinger, vstinner
Date 2021-11-25.13:26:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1637846772.99.0.18965743326.issue45476@roundup.psfhosted.org>
In-reply-to
Content
I decided to exclude macros which can be used as l-value from the PEP 670, since the motivation to disallow using them as l-value is different, and I prefer to restrict PEP 670 scope.

Disallowing using macros as l-value is more about hide implementation details and improving compatibility with Python implementations other than CPython, like PyPy or RustPython.

The PEP 670 is restricted to advantages and disavantages of converting macros to functions (static inline or regular functions).
History
Date User Action Args
2021-11-25 13:26:13vstinnersetrecipients: + vstinner, lemburg, rhettinger, mark.dickinson, gdr@garethrees.org, erlendaasland, arhadthedev
2021-11-25 13:26:12vstinnersetmessageid: <1637846772.99.0.18965743326.issue45476@roundup.psfhosted.org>
2021-11-25 13:26:12vstinnerlinkissue45476 messages
2021-11-25 13:26:12vstinnercreate