Steve,
On Tue, Apr 19, 2005 at 08:48:16AM -0400, Jason Tishler wrote:
You can workaround the problem by defining PYTHONCASEOK:
$ PYTHONCASEOK= python -c 'import bar'
$
I will work with the Python developers to try to come up with a better
long term solution.
I have found the
Jason -
Looks like just the right fix. Thanks for all the good work.
- Steve
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:
Steve,
On Fri, Apr 08, 2005 at 01:39:23PM -0400, Steve Ward wrote:
(3) Thinking that the realpath bug might be a key
to the python import-thru-symlinks problem,
I ran a simple test on recent cygwin/python
combinations, finding:
Cygwin version Python version
Steve,
On Fri, Apr 15, 2005 at 10:12:56PM -0400, Jason Tishler wrote:
On Fri, Apr 15, 2005 at 03:54:37PM -0400, Steve Ward wrote:
Can you try my failing experiment (symlink bar.py to file foo.py in
same directory)?
I was able reproduce your problem on my way out of work today.
It
On Tue, 19 Apr 2005, Jason Tishler wrote:
Steve,
On Fri, Apr 15, 2005 at 10:12:56PM -0400, Jason Tishler wrote:
On Fri, Apr 15, 2005 at 03:54:37PM -0400, Steve Ward wrote:
Can you try my failing experiment (symlink bar.py to file foo.py in
same directory)?
I was able reproduce your
On Tue, Apr 19, 2005 at 10:27:08AM -0400, Igor Pechtchanski wrote:
On Tue, 19 Apr 2005, Jason Tishler wrote:
On Fri, Apr 15, 2005 at 10:12:56PM -0400, Jason Tishler wrote:
On Fri, Apr 15, 2005 at 03:54:37PM -0400, Steve Ward wrote:
Can you try my failing experiment (symlink bar.py to file foo.py
Jason -
Thanks for all the good work. The PYTHONCASEOK workaround
indeed seems to solve the problem. From your description,
it seems that the trouble is that the real name (the name
of the symlink target) is used rather than the name of the
symlink; I should be able to circumvent naming
Jason, RE:
Sorry, but I cannot reproduce the above problem with the latest
snapshot:
$ uname -a
CYGWIN_NT-5.1 gelpdevjt022 1.5.15s(0.126/4/2) 20050408 16:35:04 ...
$ python -V
Python 2.4
$ ls -l
total 0
lrwxrwxrwx1 jtishler
Steve,
On Fri, Apr 15, 2005 at 03:54:37PM -0400, Steve Ward wrote:
Can you try my failing experiment (symlink bar.py to file foo.py in
same directory)?
I was able reproduce your problem on my way out of work today.
It seems using a different name for the symlink may cause the
trouble... I
Steve,
On Wed, Apr 06, 2005 at 05:04:52PM -0400, Steve Ward wrote:
I just upgraded to cygwin 1.5.14 from 1.5.12, and python (version 2.4
in both cases) stopped being able to import thru symlinks.
Test case: in a directory containing a symlink to foo.py,
python
import foo
RE:
I just upgraded to cygwin 1.5.14 from 1.5.12, and python
(version 2.4 in both cases) stopped being able to import
thru symlinks.
Test case: in a directory containing a symlink to foo.py,
python
import foo
complains no module named foo.py; if I copy the file to
[snip]
(3) Thinking that the realpath bug might be a key
to the python import-thru-symlinks problem,
I ran a simple test on recent cygwin/python
combinations, finding:
Cygwin version Python version realpath Import
1.5.xx: 2.yy:Works?
RE:
(3) Thinking that the realpath bug might be a key
to the python import-thru-symlinks problem,
I ran a simple test on recent cygwin/python
combinations, finding:
Cygwin version Python version realpath Import
1.5.xx:
I just upgraded to cygwin 1.5.14 from 1.5.12, and python
(version 2.4 in both cases) stopped being able to import
thru symlinks.
Test case: in a directory containing a symlink to foo.py,
python
import foo
complains no module named foo.py; if I copy the file to .,
it imports fine. Both
14 matches
Mail list logo
