[issue2921] enable embedding: declare/#define only py* symbols in #includes

STINNER Victor added the comment: Since this issue has been reported, a lot of work has been done to cleanup Python header files. In Python 3.8, we created Include/cpython/ and Include/internal/ subdirectories to clarify the intent and usage of header files. I close this issue. See bpo-2897

[issue2921] enable embedding: declare/#define only py* symbols in #includes

Changes by Bruno Dupuis : -- nosy: +bruno.dupuis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue2921] enable embedding: declare/#define only py* symbols in #includes

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue2921] enable embedding: declare/#define only py* symbols in #includes

Changes by Terry J. Reedy : -- versions: -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue2921] enable embedding: declare/#define only py* symbols in #includes

Daniel Diniz added the comment: Hallvard, There is ongoing discussion on separating public and private headers: http://groups.google.com/group/unladen-swallow/t/f3a89fc723411c49 Also see #2897, #4805, #5748 and #896330 for (sometimes slightly) related issues. -- dependencies: +include

[issue2921] enable embedding: declare/#define only py* symbols in #includes

Hallvard B Furuseth added the comment: Daniel Diniz writes: > Would this break existing code? Source code? Not if you use the PYTHON_NAMESPACE_ONLY trick. Old programs will receive all old definitions in addition to the new autoconf symbols, since they didn't #define PYTHON_NAMESPACE_ONLY. P

[issue2921] enable embedding: declare/#define only py* symbols in #includes

Daniel Diniz added the comment: Would this break existing code? Are the benefits worth it? -- nosy: +ajaksu2 priority: -> normal versions: +Python 2.7, Python 3.2 -Python 2.6 ___ Python tracker ___

[issue2921] enable embedding: declare/#define only py* symbols in #includes

Hallvard B Furuseth <[EMAIL PROTECTED]> added the comment: Duh, I should of course have said defined(PY_HAVE_ACOSH) and not defined(HAVE_ACOSH), that was the whole point:-) And the puts() should print "#define PY_HAVE_WHATEVER 1". Hopefully there are not too many #defines which would need to get

[issue2921] enable embedding: declare/#define only py* symbols in #includes

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- components: +Interpreter Core -None __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list

[issue2921] enable embedding: declare/#define only py* symbols in #includes

New submission from Hallvard B Furuseth <[EMAIL PROTECTED]>: It can be cumbersome to embed Python in a program which also #includes a config.h from autoconf, because Python's and the program's autoconf macros may interfere with each other. Assuming it compiles at all, both could define the same