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
>
> complains "no module named foo.py"; if I copy the file to ., it
> imports fine. Both worked in previous releases of cygwin.
See below...
On Fri, Apr 08, 2005 at 02:45:33PM -0400, Steve Ward wrote:
> Joerg - thanks for the suggestion. I tried the latest cygwin1.dll
> snapshot; both bugs still show up.
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
lrwxrwxrwx 1 jtishler Domain U 11 Apr 11 10:14 foo.py ->
/tmp/foo.py
$ python -c 'import foo'
$
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
