[issue20597] PATH_MAX already defined on some Windows compilers

STINNER Victor added the comment: > Reopening. I still don't understand the issue for 3.4, especially in the > light of #21274 In Python 3.5, PATH_MAX is no more used in Modules/main.c nor Python/pythonrun.c. I removed the "#define PATH_MAX ..." on Windows on Hurd. This issue is about support

[issue20597] PATH_MAX already defined on some Windows compilers

Roundup Robot added the comment: New changeset d6fb87972dee by Victor Stinner in branch 'default': Issue #20597, #21274: Remove unused definition of PATH_MAX on GNU/Hurd, https://hg.python.org/cpython/rev/d6fb87972dee -- ___ Python tracker

[issue20597] PATH_MAX already defined on some Windows compilers

Roundup Robot added the comment: New changeset 6aaa0aab1e93 by Victor Stinner in branch 'default': Issue #20597: Remove unused definition of PATH_MAX on Windows, MAXPATHLEN is https://hg.python.org/cpython/rev/6aaa0aab1e93 -- nosy: +python-dev ___ Pyt

[issue20597] PATH_MAX already defined on some Windows compilers

Jeffrey Armstrong added the comment: What's to understand? Some compilers, particularly MinGW and Open Watcom, already define a PATH_MAX macro on Windows, and it's not necessarily the same as Python's redefinition of it, possibly causing a compiler error. That's all. Given the time frame tha

[issue20597] PATH_MAX already defined on some Windows compilers

Martin v. Löwis added the comment: Reopening. I still don't understand the issue for 3.4, especially in the light of #21274 -- status: closed -> open ___ Python tracker ___

[issue20597] PATH_MAX already defined on some Windows compilers

Changes by Jeffrey Armstrong : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue20597] PATH_MAX already defined on some Windows compilers

Jeffrey Armstrong added the comment: Was this ever accepted? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20597] PATH_MAX already defined on some Windows compilers

Larry Hastings added the comment: Assuming you keep an eye on the buildbots, this has my permission to go in. Martin: While we don't officially support those compilers, I don't see the harm of removing unused #defines, so I'm willing to accept it for rc2. -- __

[issue20597] PATH_MAX already defined on some Windows compilers

Jeffrey Armstrong added the comment: PATH_MAX is defined in both Open Watcom and MinGW's GCC toolchain. Neither is a "supported" compiler, I suppose. I hadn't meant to suggest that it be included in 3.4's release candidate, only that the problem exists on current versions. -- _

[issue20597] PATH_MAX already defined on some Windows compilers

Martin v. Löwis added the comment: Jeffrey: Which compilers specifically? It's probably not MSVC, hence it's not a "supported" compiler, and IMO shouldn't go in after the release candidate for 3.4. -- ___ Python tracker

[issue20597] PATH_MAX already defined on some Windows compilers

STINNER Victor added the comment: I found it: changeset: 87113:159e51e5fc2c branch: 3.3 parent: 87102:46fc4fb2c8c5 user:Victor Stinner date:Fri Nov 15 17:09:24 2013 +0100 files: Python/pythonrun.c description: pythonrun.c: fix Py_GetPythonHome(), use Py_ARRAY_L

[issue20597] PATH_MAX already defined on some Windows compilers

STINNER Victor added the comment: > Let's be a little smarter. PATH_MAX isn't used anymore. Just remove the > #defines entirely. Oh I remember that I replaced PATH_MAX with MAXPATHLEN or maybe something else when I tried to fix Python compilation issue on our IRIX buildbot :-) remove_path_m

[issue20597] PATH_MAX already defined on some Windows compilers

Jeffrey Armstrong added the comment: Here's an additional patch removing PATH_MAX from Modules/main.c and Python/pythonrun.c. This solution works fine for me. -- Added file: http://bugs.python.org/file34044/remove_path_max.default.patch ___ Python t

[issue20597] PATH_MAX already defined on some Windows compilers

Larry Hastings added the comment: Let's be a little smarter. PATH_MAX isn't used anymore. Just remove the #defines entirely. -- ___ Python tracker ___

[issue20597] PATH_MAX already defined on some Windows compilers

STINNER Victor added the comment: The patch is simple and looks safe. I'm in favor of applying it on Python 3.3 and 3.4. (Python 2.7 is not affect.) @Larry: ok for Python 3.4? -- nosy: +haypo, larry, loewis, serhiy.storchaka ___ Python tracker

[issue20597] PATH_MAX already defined on some Windows compilers

New submission from Jeffrey Armstrong: On some Windows compilers, the constant PATH_MAX may already be defined, which will cause compile errors on non-MSVC compilers (notably Open Watcom and MinGW). Rather than assume it is not available and define it in all "#ifdef MS_WINDOWS" cases, it shou