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 kristjan.jonsson
Recipients Arfrever, benjamin.peterson, brett.cannon, georg.brandl, kristjan.jonsson, larry, loewis, pitrou, rhettinger, serhiy.storchaka, skrah, taleinat, vstinner
Date 2014-02-27.10:07:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well, Larry, I certainly am in no mood to start wrangling on python-dev.  A 25 year old C standard is likely to be very mature and reliable by now.  Why take risks? :)

#Py_LOCAL_INLINE exists and demonstrates that we can make use of them when possible.
We could create a #Py_INLINE macro that would work the same, only not necessarily yield inline on some of the older compilers.

It would really be healthy for the pyton code base, for quality, for semantics, and for the learning curve, if we could start to rely less on macros in the core.

Ah well, perhaps I'll throw this out there...
Date User Action Args
2014-02-27 10:07:45kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, brett.cannon, georg.brandl, rhettinger, pitrou, vstinner, taleinat, larry, benjamin.peterson, Arfrever, skrah, serhiy.storchaka
2014-02-27 10:07:45kristjan.jonssonsetmessageid: <>
2014-02-27 10:07:45kristjan.jonssonlinkissue20440 messages
2014-02-27 10:07:44kristjan.jonssoncreate