Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #93142 > unrolled thread

Re: windows and file names > 256 bytes

Started byTim Golden <mail@timgolden.me.uk>
First post2015-06-25 14:37 +0100
Last post2015-06-25 14:37 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: windows and file names > 256 bytes Tim Golden <mail@timgolden.me.uk> - 2015-06-25 14:37 +0100

#93142 — Re: windows and file names > 256 bytes

FromTim Golden <mail@timgolden.me.uk>
Date2015-06-25 14:37 +0100
SubjectRe: windows and file names > 256 bytes
Message-ID<mailman.67.1435239479.3674.python-list@python.org>
On 25/06/2015 14:35, Michael Torrie wrote:
> On 06/25/2015 06:34 AM, Tim Golden wrote:
>> On 25/06/2015 13:04, Joonas Liik wrote:
>>> It sounds to me more like it is possible to use long file names on windows
>>> but it is a pain and in python, on windows it is basically impossible.
>>
>> Certainly not impossible: you could write your own wrapper function:
>>
>> def extended_path(p):
>>     return r"\\?\%s" % os.path.abspath(p)
>>
>> where you knew that there was a possibility of long paths and that an
>> absolute path would work.
> 
> The OP mentions that even when he manually supplies extended paths,
> os.mkdir, os.getsize, and shutil.rmtree return errors for him in Python
> 2.7.  So there's more to this problem.
> 

He's probably not passing unicode strings: the extended path only works
for unicode string. For 3.x that's what you do by default.

TJG

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web