Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 To: cygwin AT cygwin DOT com cc: joerg DOT schaible AT gmx DOT de In-reply-to: (message from Steve Ward on Fri, 08 Apr 2005 13:39:23 -0400) Subject: Re: Symlinks don't work in python??? Reply-to: ward AT mit DOT edu References: Message-Id: Date: Fri, 08 Apr 2005 14:45:33 -0400 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: 2.yy: Works? Works? > -------------- -------------- -------- ------ > > 1.5.14 2.4 NO NO > 1.5.13 2.3.4 YES NO > 1.5.14 2.3.4 YES NO > 1.5.12 2.4 NO YES > > Neither bug shows up under Linux. > > Interestingly, the realpath and symlink bugs don't > correlate: realpath seems broken in Cygwin python 2.4, > independently of the cygwin package version, while > the import bug shows up in either python version under > cygwin packages since 1.5.13. > > Its possible that the problems are python bugs, but they > seem cygwin specific. Steve, try also the latest cygwin snapshot. At least in 1.5.14 was a bug concerning path conversion posix <-> Windows, when a symlink was involved. It manifests in at least in cygpath, but is fixed meanwhile and might also have influence on your test cases. - Joerg Joerg - thanks for the suggestion. I tried the latest cygwin1.dll snapshot; both bugs still show up. - Steve -- 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/