#39 — Unable to install ZopeSkel on Windows due to long filenames OR special chars
by
Sridhar Ratnakumar
—
last modified
Mar 23, 2010 10:50 PM
| State | Unconfirmed |
|---|---|
| Version: | 2.16 |
| Area | General |
| Issue type | Bug |
| Severity | Low |
| Submitted by | Sridhar Ratnakumar |
| Submitted on | Mar 23, 2010 |
| Responsible |
—
|
| Target release: |
—
|
From http://pypm-free.activestate.com/[…]/log
[...]
copying build\lib\zopeskel\templates\kss_plugin\+namespace_package+\+namespace_package2+\+package+\+namespace_package+.+namespace_package2+.+package+-configure.zcml_tmpl -> _pypm_install_root\ActivePython32Python26\Lib\site-packages\zopeskel\templates\kss_plugin\+namespace_package+\+namespace_package2+\+package+
error: _pypm_install_root\ActivePython32Python26\Lib\site-packages\zopeskel\templates\kss_plugin\+namespace_package+\+namespace_package2+\+package+\+namespace_package+.+namespace_package2+.+package+-configure.zcml_tmpl: No such file or directory
[...]
copying build\lib\zopeskel\templates\kss_plugin\+namespace_package+\+namespace_package2+\+package+\+namespace_package+.+namespace_package2+.+package+-configure.zcml_tmpl -> _pypm_install_root\ActivePython32Python26\Lib\site-packages\zopeskel\templates\kss_plugin\+namespace_package+\+namespace_package2+\+package+
error: _pypm_install_root\ActivePython32Python26\Lib\site-packages\zopeskel\templates\kss_plugin\+namespace_package+\+namespace_package2+\+package+\+namespace_package+.+namespace_package2+.+package+-configure.zcml_tmpl: No such file or directory
- Steps to reproduce:
- Just try to create a virtualenv in long path name directory and try to install ZopeSkel in it.
Added by
Cris Ewing
on
Mar 23, 2010 09:45 PM
I'm not certain what to do about this. I've attached the log file pointed to above (in case it disappears from view at some point). The file in question is copied from one place to another twice in the log file before it finally fails this final time. Can we get confirmation from another windows user that the issue is a problem for them, too?
Severity:
Medium
→
Low
It would be appreciated if someone who actually uses zopeskel on win32 could chime in and help figure out what the problem is here. The theory that it's the length of the pathname or the special characters seems plausible, but I'm not sure what we can do to alleviate the problem. It's the nature of the beast here that we have to use special characters in filenames and because many of the file structures are deeply nested, there probably isn't much of a way to get around the length of the pathnames.
Any ideas out there for solutions?
Added by
Cris Ewing
on
Mar 23, 2010 10:50 PM
No responses can be added.
If you can, please log in before submitting a reaction.

