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 aeros
Recipients Greg Price, aeros, malin, mark.dickinson, rhettinger, sir-sigurd, tim.peters, vstinner
Date 2019-09-20.22:32:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1569018736.78.0.0161538058622.issue37812@roundup.psfhosted.org>
In-reply-to
Content
> You can find my email in Git, and I'm on Zulip and Discourse; and I'd be happy to start or follow a thread in a forum you think appropriate.  Or if you'd rather drop it entirely, that's fine too.

I think opening a thread in https://discuss.python.org/c/users to talk about deciding between the usage of functions and macros (discussing when each may be appropriate) would be beneficial to the community at large.

> The recommendation of the senior most developer is being ignored, and now two developers are speaking in terms of strong belief systems and labeling long-stable code as "evil".  This doesn't bode well and it makes it difficult to conduct reasoned discourse.  

Apologies if I added to that, I certainly respect your judgement on this issue. Pretty much everyone involved in this discussion has more experience in working with the CPython C-API than I do, you most of all (as far I'm aware). My perspective was coming from someone attempting to understand it better, and explaining how those learning the C-API might find it confusing.

I don't find the code itself to be at all "evil", just potentially confusing. That long-stable code has provided a lot of benefit over the years, and I can definitely appreciate the effort that was put into writing it.
History
Date User Action Args
2019-09-20 22:32:16aerossetrecipients: + aeros, tim.peters, rhettinger, mark.dickinson, vstinner, malin, Greg Price, sir-sigurd
2019-09-20 22:32:16aerossetmessageid: <1569018736.78.0.0161538058622.issue37812@roundup.psfhosted.org>
2019-09-20 22:32:16aeroslinkissue37812 messages
2019-09-20 22:32:16aeroscreate