Opened 18 years ago
Closed 18 years ago
#4847 closed defect (worksforme)
Initenv on cygwin uses wrong
Reported by: | Tim Hatch | Owned by: | Christopher Lenz |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | admin/console | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Reported in person at the sprint.
Using Bash in cygwin (just installed). Python 2.5 for Windows. Followed directions in TracOnWindows for Python 2.5
Specified initenv using forward slashes, os.mkdir in env.py:create fails (tries to use Windows backslashes).
I don't know if this is reproducible because I don't run Windows.
Attachments (0)
Change History (3)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
Further information, it works fine when you specify the full path, but ~/path triggers the issue.
comment:3 by , 18 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
~/path
should not be used, as it expands to /C/...
something, i.e. a cygwin path, which of course Python has not idea about (unless it would be the Cygwin python.exe
but that has never been tested AFAIK ;-) ).
If you absolutely want to use a path relative to ~
, use e.g. $(cygpath -m ~/path)
.
Are you sure it's the current python.exe that get used? (i.e. not the cygwin one)
I just tried, also at the cygwin Bash prompt:
and it worked:
(ok, that was with 2.4, not 2.5)