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 ezio.melotti ezio.melotti, loewis, ocean-city, pitrou, r.david.murray 2009-05-04.06:21:29 0.000304838 No <1241418119.42.0.0895500663113.issue5913@psf.upfronthosting.co.za>
Content
> It is normal behavior for Windows.  Try it with the 'dir' command
> in a command window.  (That said, I have no idea, not being a
> Windows user, how Windows decides what the 'current' directory
> is on any given drive from any given context).

Yes, I tried to run cmd.exe and I did:

C:\> cd D:\foo
C:\> cd E:\foo
C:\> python

os.listdir('D:') and os.listdir('E:') then listed the content of D:\foo
and E:\bar. This is the correct behaviour, even if it's not documented.
The CWD is the one where Python has been launched, and apparently on the
other drives is the root folder by default, if it's not changed with the
cd command.

Thanks Hirokazu for the patch.
History
Date User Action Args
2009-05-04 06:22:01ezio.melottisetrecipients: + ezio.melotti, loewis, pitrou, ocean-city, r.david.murray
2009-05-04 06:21:59ezio.melottisetmessageid: <1241418119.42.0.0895500663113.issue5913@psf.upfronthosting.co.za>