On Wed, Mar 21, 2018 at 10:58 AM, Chris Billington < [email protected]> wrote:
> I don't think that's true: > > > > On Wed, Mar 21, 2018 at 10:51 AM, Greg Ewing <[email protected]> > wrote: > >> Chris Billington wrote: >> >>> I wonder how mercurial gets around the fact that its own imports might >>> be shadowed by whatever's in the current working directory. >>> >> >> The cwd is only added to sys.path in the interactive interpreter, >> not when you run "python something.py". So it's not usually a >> problem for applications implemented in Python. >> >> > I don't think that's true: > > $ cd /tmp > $ echo 'import bar' > foo.py > $ echo 'print("this is bar")' > bar.py > $ python foo.py > this is bar > > (/tmp is not in the python path) > > Actually I'm mistaken. That's the directory of the script being added to the path, not the current working directory. -Chris > >> -- >> Greg >> >> _______________________________________________ >> Python-ideas mailing list >> [email protected] >> https://mail.python.org/mailman/listinfo/python-ideas >> Code of Conduct: http://python.org/psf/codeofconduct/ >> > >
_______________________________________________ Python-ideas mailing list [email protected] https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
