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 hoffman
Recipients Anthony Sottile, bradengroom, hoffman, loewis, serhiy.storchaka, vstinner
Date 2018-10-29.00:29:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1564-1540772960-49936@sneakemail.com>
In-reply-to <1540762045.16.0.788709270274.issue1154351@psf.upfronthosting.co.za>
Content
glibc `getcwd()` and `get_current_dir_name()` are not the same. glibc
`get_current_dir_name()` does, in fact, check the `PWD` environment
variable.

https://www.gnu.org/software/libc/manual/html_node/Working-Directory.html

The get_current_dir_name function is basically equivalent to
getcwd (NULL, 0), except the value of the PWD environment variable is first
examined, and if it does in fact correspond to the current directory, that
value is returned. This is a subtle difference which is visible if the path
described by the value in PWD is using one or more symbolic links, in which
case the value returned by getcwd would resolve the symbolic links and
therefore yield a different result.

On Sun, Oct 28, 2018 at 5:27 PM Braden Groom report-at-bugs.python.org
|Python/Example Allow| <16snny1crx82vlt@sneakemail.com> wrote:

>
> Braden Groom <braden.groom@gmail.com> added the comment:
>
> Victor, FWIW I don't need this functionality and your suggestion on the PR
> seems reasonable to me. I only picked up this issue as a way to become
> familiar with contributing to the project. I'm okay with closing both the
> PR and the ticket.
>
> ----------
> nosy: +bradengroom
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue1154351>
> _______________________________________
>
History
Date User Action Args
2018-10-29 00:29:24hoffmansetrecipients: + hoffman, loewis, vstinner, serhiy.storchaka, Anthony Sottile, bradengroom
2018-10-29 00:29:24hoffmanlinkissue1154351 messages
2018-10-29 00:29:24hoffmancreate