Message94199
| Author |
swarecki |
| Recipients |
brett.cannon, ezio.melotti, markon, swarecki |
| Date |
2009年10月18日.03:00:10 |
| SpamBayes Score |
6.896393e-08 |
| Marked as misclassified |
No |
| Message-id |
<4ADA84D8.8060000@cox.net> |
| In-reply-to |
<1255792525.17.0.933244336721.issue6975@psf.upfronthosting.co.za> |
| Content |
Marco,
Thanks for looking deeper into it.
I would like to check the solution ASAP.
We have really crazy dir structure which can catch a lot of
the unexpected problems with paths, links, circular links etc.
Should I expect the new version to generate the exception
as you suggested?
Best Regards,
Sywlester Warecki
Marco Buccini wrote:
> Marco Buccini <marcusbu@gmail.com> added the comment:
>
> I've just found a similar bug:
> http://bugs.python.org/issue1646838
>
> However, does os.path.realpath's behavior have to be as the one
> specified by the POSIX standard (
> http://www.kernel.org/doc/man-pages/online/pages/man3/realpath.3.html )?
> If we wanted to follow the standard, we should break the
> retro-compatibility, since we should raise an exception in the case the
> path passed as argument doesn't exist.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue6975>
> _______________________________________
>
> |
|