[issue17791] PC/pyconfig.h defines PREFIX macro

Roundup Robot added the comment: New changeset fbd856e817a1 by Christian Heimes in branch 'default': Issue #17791: Drop PREFIX and EXEC_PREFIX definitions from PC/pyconfig.h http://hg.python.org/cpython/rev/fbd856e817a1 -- nosy: +python-dev ___ Python

[issue17791] PC/pyconfig.h defines PREFIX macro

Changes by Christian Heimes : -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___

[issue17791] PC/pyconfig.h defines PREFIX macro

Christian Heimes added the comment: I'll remove the offending lines later. -- assignee: -> christian.heimes ___ Python tracker ___ __

[issue17791] PC/pyconfig.h defines PREFIX macro

Christian Heimes added the comment: Fantastic! Does anybody know anything about Cygwin builds? I expect that Cygwin uses autoconf to generate its own pyconfig.h. -- ___ Python tracker _

[issue17791] PC/pyconfig.h defines PREFIX macro

Tim Golden added the comment: Ok by me: build and tests all ok. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue17791] PC/pyconfig.h defines PREFIX macro

Christian Heimes added the comment: ping RMs and Windows devs -- nosy: +brian.curtin, larry, tim.golden ___ Python tracker ___ ___ Pyt

[issue17791] PC/pyconfig.h defines PREFIX macro

Christian Heimes added the comment: It looks like we can drop PREFIX and EXEC_PREFIX from PC/pyconfig.h all along. Only Modules/getpath.c uses PREFIX and EXEC_PREFIX but MSVC build use PC/getpathp.c instead of Modules/getpath.c -- ___ Python tracker

[issue17791] PC/pyconfig.h defines PREFIX macro

New submission from Christian Heimes: The pyconfig.h file of the Windows build environment defines at least two macros without a Py/PY prefix: PC/pyconfig.h:#define PREFIX "" PC/pyconfig.h:#define EXEC_PREFIX "" This has caused multiple issues in the past. For example libexpat uses PREFIX, to