Windows path names use broken shortnames
Bug #419040 reported by
Stuart
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Virtualenv |
New
|
Undecided
|
Unassigned | ||
Bug Description
The paths that are embedded in a windows virtualenv setup appear to use windows short filenames - this creates a problem when backingup/restoring enviroments as the windows short filenames can change.
In my case a path of c:/projects/
If this is zipped, and then unzipped in a new empty c:/projects directory (on ntfs), the shortcut is not /projects/stream~1 and does not work. This is as far as I can tell no way to then heal it as the paths are not accessible.
These days is there really any reason to use the short compatible filenames? we have not used them in our products for years.
Revision history for this message
| Carl Meyer (carljm) wrote | #1 |
To post a comment you must log in.
Moved to https:/