Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #93137 > unrolled thread
| Started by | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| First post | 2015-06-25 08:41 -0400 |
| Last post | 2015-06-25 08:41 -0400 |
| 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.
Re: windows and file names > 256 bytes Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2015-06-25 08:41 -0400
| From | Dennis Lee Bieber <wlfraed@ix.netcom.com> |
|---|---|
| Date | 2015-06-25 08:41 -0400 |
| Subject | Re: windows and file names > 256 bytes |
| Message-ID | <mailman.62.1435236090.3674.python-list@python.org> |
On Thu, 25 Jun 2015 15:04:37 +0300, Joonas Liik <liik.joonas@gmail.com>
declaimed the following:
>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.
>
>So shouldn't it be possible to maniulate these files with extended names..
>
>I mean even if you had to use some special function to ask for long names
>it would still be better than no support at all.
A single long filename is not a problem... It is the combined
path/filename that becomes a problem. And It is not just a problem with
Python -- I've had Windows copy command fail when run recursively for the
same situation; either the source or destination path/name combination
becomes too long to handle.
One can "cd" down a few levels of the path, and then rename a directory
up to the root level -- then all subsequent paths are shorter.
--
Wulfraed Dennis Lee Bieber AF6VN
wlfraed@ix.netcom.com HTTP://wlfraed.home.netcom.com/
Back to top | Article view | comp.lang.python
csiph-web