Author vstinner
Recipients lkollar, ncoghlan, ned.deily, pablogsal, ronaldoussoren, vstinner
Date 2019-03-12.15:57:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1552406223.06.0.726409960411.issue36236@roundup.psfhosted.org>
In-reply-to
Content
_Py_wgetcwd() call has been introduced by the following commit:

commit ee3784594b33c72c3fdca6a71892d22f14045ab6
Author: Nick Coghlan <ncoghlan@gmail.com>
Date:   Sun Mar 25 23:43:50 2018 +1000

    bpo-33053: -m now adds *starting* directory to sys.path (GH-6231) (#6236)
    
    Historically, -m added the empty string as sys.path
    zero, meaning it resolved imports against the current
    working directory, the same way -c and the interactive
    prompt do.
    
    This changes the sys.path initialisation to add the
    *starting* working directory as sys.path[0] instead,
    such that changes to the working directory while the
    program is running will have no effect on imports
    when using the -m switch.
    
    (cherry picked from commit d5d9e02dd3c6df06a8dd9ce75ee9b52976420a8b)

I don't think that it's correct to fail with a fatal error if the current directory no longer exist. Would it be possible to not add it to sys.path if it doesn't exist? Silently ignore the error.

@Nick: What do you think?
History
Date User Action Args
2019-03-12 15:57:03vstinnersetrecipients: + vstinner, ronaldoussoren, ncoghlan, ned.deily, lkollar, pablogsal
2019-03-12 15:57:03vstinnersetmessageid: <1552406223.06.0.726409960411.issue36236@roundup.psfhosted.org>
2019-03-12 15:57:03vstinnerlinkissue36236 messages
2019-03-12 15:57:02vstinnercreate