[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2235: Error from 'tahoe cp' on Windows, possibly due to a long path (IOError: Errno2 - no such file or dir.)

[Tahoe-LAFS]

#2235: Error from 'tahoe cp' on Windows, possibly due to a long path (IOError:
Errno2 - no such file or dir.)
--------------------------------+------------------------------------------
     Reporter:  CyberAxe        |      Owner:  daira
         Type:  defect          |     Status:  new
     Priority:  normal          |  Milestone:  undecided
    Component:  code-frontend-  |    Version:  1.10.0
  cli                           |   Keywords:  tahoe-cp error windows win32
   Resolution:                  |
Launchpad Bug:                  |
--------------------------------+------------------------------------------

Comment (by daira):

 Replying to [comment:4 zooko]:
 > Why can't we just prepend "`\\?\`" to the string before we pass it to
 {{{open()}}} on line 274 of
 [source:trunk/src/allmydata/util/fileutil.py?rev=ff64a0fef5879d3651bc3db6ca0522d96b217d45
 fileutil.py]?

 It's not quite as simple as that:

 * Paths prefixed with "`\\?\`" must be absolute, but CLI commands accept
 relative paths.
 * "`\\?\`" is only supported by the Unicode Win32 file APIs. I think
 Python does use those APIs (indirectly, via msvcrt) when given a `unicode`
 string, though.
 * For consistency you'd need to change many other places in Tahoe-LAFS
 that access files, even to just support long paths in CLI commands.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2235#comment:5>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage