Message 230673 - Python tracker

➜

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.

In-reply-to
Author	Jeffrey.Armstrong
Recipients	Jeffrey.Armstrong, larry, loewis, serhiy.storchaka, vstinner
Date	2014年11月05日.11:27:00
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1415186820.95.0.437469331823.issue20597@psf.upfronthosting.co.za>

Content
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 that this bug has existed (9 months!?!) and its trivial fix, which would involve adding an "#ifndef PATH_MAX" right before its declaration, I think "won't fix" is an appropriate resolution. Leave it open or don't, it makes little difference to me as I'm no longer interested.

Content

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 that this bug has existed (9 months!?!) and its trivial fix, which would involve adding an "#ifndef PATH_MAX" right before its declaration, I think "won't fix" is an appropriate resolution.
Leave it open or don't, it makes little difference to me as I'm no longer interested.

History
Date	User	Action	Args
2014年11月05日 11:27:01	Jeffrey.Armstrong	set	recipients: + Jeffrey.Armstrong, loewis, vstinner, larry, serhiy.storchaka
2014年11月05日 11:27:00	Jeffrey.Armstrong	set	messageid: <1415186820.95.0.437469331823.issue20597@psf.upfronthosting.co.za>
2014年11月05日 11:27:00	Jeffrey.Armstrong	link	issue20597 messages
2014年11月05日 11:27:00	Jeffrey.Armstrong	create

homepage