>> Header Files and Preprocessor Definitions >> ----------------------------------------- >> >> Applications shall only include the header file Python.h (before >> including any system headers), or, optionally, include pyconfig.h, and >> then Python.h. > > What about structmember.h? It's not yet included with Python.h AFAICS.
Right - I think it should be, though. Is there a reason why it's not included? The only reason I can see is that it isn't completely namespace-safe, e.g. it defines a constant READONLY. Not sure whether the T_ constants would need to be changed as well. So if that's the rationale, I would propose to make it namespace-safe under a different file name, and add alias #defines in structmember.h for compatibility. I also think this should happen independent of PEP 384. See also issue 2897 - perhaps we can even fix it for 3.1. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
