Message 87080 - Python tracker

➜

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	r.david.murray
Recipients	ezio.melotti, loewis, pitrou, r.david.murray
Date	2009-05-03.22:22:05
SpamBayes Score	0.00022958826
Marked as misclassified	No
Message-id	<Pine.LNX.4.64.0905031809500.3802@kimball.webabinitio.net>
In-reply-to	<1241372216.49.0.847578529009.issue5913@psf.upfronthosting.co.za>

Content
On Sun, 3 May 2009 at 17:36, Antoine Pitrou wrote: > As for the "C:" behaviour, I think it is normal: you are not specifying > the path itself, only the drive letter, so it uses the current path in > the specified drive (which /is/ cwd if you are already running from C:, > but may be something else if running from another drive). 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).

On Sun, 3 May 2009 at 17:36, Antoine Pitrou wrote:
> As for the "C:" behaviour, I think it is normal: you are not specifying
> the path itself, only the drive letter, so it uses the current path in
> the specified drive (which /is/ cwd if you are already running from C:,
> but may be something else if running from another drive).

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).

History
Date	User	Action	Args
2009-05-03 22:22:07	r.david.murray	set	recipients: + r.david.murray, loewis, pitrou, ezio.melotti
2009-05-03 22:22:06	r.david.murray	link	issue5913 messages
2009-05-03 22:22:05	r.david.murray	create