Message 146424 - 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	ishimoto
Recipients	ishimoto, terry.reedy, ubershmekel, vstinner
Date	2011-10-26.08:01:33
SpamBayes Score	7.4927193e-06
Marked as misclassified	No
Message-id	<CAK2Ax-WKkPmQpPB9F1R_DjxY82jzLfHPQ1Ye9YeShxmt-_b9Qw@mail.gmail.com>
In-reply-to	<1319610993.02.0.935018614875.issue13247@psf.upfronthosting.co.za>

Content
On Wed, Oct 26, 2011 at 3:36 PM, Yuval Greenfield <report@bugs.python.org> wrote: > If the current situation isn't fixed though - you just can't use the resulting path for almost anything. Do you have a use case Ishimoto? I don't have use case. But does raising UnicodeEncodeError fix problems? It could break existing code, but I don't see much difference over WindowsError caused by the broken file names. > The fact is you shouldn't be doing os.path.abspath(b'.') in windows to begin with. Agreed. So I think adding Windows specific check to Byte API does not improve situation, but increase complexity of std lib.

On Wed, Oct 26, 2011 at 3:36 PM, Yuval Greenfield
<report@bugs.python.org> wrote:

> If the current situation isn't fixed though - you just can't use the resulting path for almost anything. Do you have a use case Ishimoto?

I don't have use case. But does raising UnicodeEncodeError fix
problems?  It could break existing code, but I don't see much
difference over WindowsError caused by the broken file names.

> The fact is you shouldn't be doing os.path.abspath(b'.') in windows to begin with.

Agreed. So I think adding Windows specific check to Byte API does not
improve situation, but increase complexity of std lib.

History
Date	User	Action	Args
2011-10-26 08:01:34	ishimoto	set	recipients: + ishimoto, terry.reedy, vstinner, ubershmekel
2011-10-26 08:01:33	ishimoto	link	issue13247 messages
2011-10-26 08:01:33	ishimoto	create