➜

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 neologix
Recipients eric.araujo, matejcik, neologix, pitrou, rosslagerwall, santoso.wijaya, vstinner
Date 2011-08-29.17:22:18
SpamBayes Score 9.059913e-05
Marked as misclassified No
Message-id <CAH_1eM0Okeq30F_5YYviCRaxuu1aW1KS8CYkMJv6vYG=JY-W9Q@mail.gmail.com>
In-reply-to <1314634033.05.0.557141382786.issue12801@psf.upfronthosting.co.za>
Content 
> Well, if we use two different paths based on the libc version, it might not be a good idea, since behaviour can be different in some cases.

Indeed.

> It would be nice to know if some modern platforms have a non-compliant realpath().

Alas, it doesn't seem to hold for OpenBSD:
http://old.nabble.com/Make-realpath(3)-conform-to-SUSv4-td32031895.html

A patch supporting NULL was committed two months ago, which means we
probably can't push this forward.

I've been quite disappointed by POSIX lately...
History
Date User Action Args
2011-08-29 17:22:19neologixsetrecipients: + neologix, pitrou, vstinner, matejcik, eric.araujo, santoso.wijaya, rosslagerwall
2011-08-29 17:22:18neologixlinkissue12801 messages
2011-08-29 17:22:18neologixcreate