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.

Author movement
Recipients loewis, movement, zooko
Date 2009-02-16.14:26:58
SpamBayes Score 1.0550131e-06
Marked as misclassified No
Message-id <1234794524.57.0.805130533492.issue1759169@psf.upfronthosting.co.za>
In-reply-to
Content
Zooko, the patches are available here:

http://src.opensolaris.org/source/xref/jds/spec-files/trunk/patches/

> Then you were arguing that defining _XOPEN_SOURCE is wrong if the value

Actually, I was saying that below that value simply won't work for many
extensions.

> What about setting the value to 600 or larger? Is that also wrong,
> and if so, why?

Practically: I don't know for sure about a larger value. As it is
presumably very close to POSIX, it shouldn't significantly harm the
ability to compile stuff. I can't say for sure. However, specifying
_XOPEN_SOURCE is still unnecessary I believe.

Theoretically: yes, it's wrong for Python to claim that all extensions
are compliant to a particular XPG environment.

If it helps, Martin, I can put you in touch with our standards expert.
I'm far from such, so this might help assuage your doubts?
History
Date User Action Args
2009-02-16 14:28:44movementsetrecipients: + movement, loewis, zooko
2009-02-16 14:28:44movementsetmessageid: <1234794524.57.0.805130533492.issue1759169@psf.upfronthosting.co.za>
2009-02-16 14:26:59movementlinkissue1759169 messages
2009-02-16 14:26:58movementcreate