Modules/getpath.c chases links?

Edward Jason Riedy ejr at CS.Berkeley.EDU
Sun Nov 28 02:46:20 EST 1999

Is there a reason why Modules/getpath.c chases links to get the
`correct' path?  I'd like to see that removed, but the comments
make me think someone had a specific reason for including it.

I use symlink trees to separate out different versions of packages 
distributed by different people (here, stock python 1.5.2 and the
LLNL-distributed  NumPy).  The symlink chasing breaks this badly
by looking into the symlinked directory rather than using the tree
of symlinks.

Simply removing the code protected by HAVE_READLINK makes my life 
much nicer.  I'd really like to see it officially removed.  (If you
want a full-featured system for finding the installation, check the
kpathsea library in the Web2C distribution of TeX.)

Jason (not subscribed, please cc)

More information about the Python-list mailing list