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 Mail-Followup-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com From: =?ISO-8859-1?Q?J=F6rg?= Schaible Subject: Re: Symlinks don't work in python??? Date: Fri, 08 Apr 2005 19:16:37 +0200 Lines: 33 Message-ID: References: Reply-To: joerg DOT schaible AT gmx DOT de Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8Bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: p549aa6ed.dip0.t-ipconnect.de Mail-Copies-To: never User-Agent: KNode/0.8.2 X-IsSubscribed: yes [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? 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. - Jörg -- 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/