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 pitrou
Recipients eric.snow, jkloth, ncoghlan, pitrou, serhiy.storchaka, vstinner, yselivanov
Date 2017-07-06.22:08:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499378919.38.0.630578077035.issue30860@psf.upfronthosting.co.za>
In-reply-to
Content
After looking at the PR, I'm a bit skeptical about this.  Suddenly a lot of things which are implementation details get moved to the public include files, which makes things more confusing from my POV.  I also don't know why all globals should be consolidated in a single place (it is not a widespread policy in other projects AFAIK, but I may be mistaken).

Perhaps it would be more reasonable to consolidate the globals in each .c file independently, without trying to join all of them together in one place nor expose them in the public include files.
History
Date User Action Args
2017-07-06 22:08:39pitrousetrecipients: + pitrou, ncoghlan, vstinner, jkloth, eric.snow, serhiy.storchaka, yselivanov
2017-07-06 22:08:39pitrousetmessageid: <1499378919.38.0.630578077035.issue30860@psf.upfronthosting.co.za>
2017-07-06 22:08:39pitroulinkissue30860 messages
2017-07-06 22:08:39pitroucreate