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 loewis
Recipients loewis, ocean-city, pitrou
Date 2010-12-05.19:21:17
SpamBayes Score 4.3452e-06
Marked as misclassified No
Message-id <1291576879.4.0.960141480079.issue10631@psf.upfronthosting.co.za>
In-reply-to
Content
More formally: it's unspecified. I'd like to propose this general principle: If you pass a relative path to some library that gets stored in the library, it's unspecified whether the cwd is consider at the point of passing the path or at the point of using it in some operation.

Applications that want to be cwd-agnostic must always use abspath.

The only exceptions are operations where there is some explicit open() operation that is documented to interpret the path name; for these, it is clear that the cwd is considered inside the open().
History
Date User Action Args
2010-12-05 19:21:19loewissetrecipients: + loewis, pitrou, ocean-city
2010-12-05 19:21:19loewissetmessageid: <1291576879.4.0.960141480079.issue10631@psf.upfronthosting.co.za>
2010-12-05 19:21:18loewislinkissue10631 messages
2010-12-05 19:21:18loewiscreate