delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
From: | Steve Ward <ward AT csail DOT mit DOT edu> |
To: | cygwin AT cygwin DOT com |
Subject: | Symlinks don't work in python??? |
Reply-to: | ward AT mit DOT edu |
Message-Id: | <E1DJHhk-0000GC-VY@cag.csail.mit.edu> |
Date: | Wed, 06 Apr 2005 17:04:52 -0400 |
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. Similarly, putting symlinks in site-packages no longer works. Has some change to cygwin's handling of symlinks (since 1.5.12) caused this problem? Thanks for any light shed... - Steve Ward -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |