OK, I attach a fairly minimal python package. It builds fine normally. Now, if you add a broken symlink in the source tree, it fails to build. For example, "ln -s /broken broken.symlink" in the same directory as setup.py.
Phillip J. Eby wrote: > At 12:23 PM 6/25/2007 -0700, Andrew Straw wrote: >> In setuptools 0.6c5, a broken symlink in the package tree will cause >> 'setup develop' to fail, even in the file is inconsequential for the >> package. I think this is a bug. >> >> Here is the output of running "python setup.py develop" in a package >> called flydra with a broken symlink called broken.symlink: >> >> running develop >> running egg_info >> writing flydra.egg-info/PKG-INFO >> writing top-level names to flydra.egg-info/top_level.txt >> writing dependency_links to flydra.egg-info/dependency_links.txt >> writing entry points to flydra.egg-info/entry_points.txt >> error: broken.symlink: No such file or directory >> >> (I would try this using setuptools==dev, but it seems svn.python.org is >> down, or at least my connection to it.) > > Uh, where is this broken symlink exactly, and what does it point to? > What is the contents of your setup.py? IOW, a minimal data set for > reproducing the error would be helpful, as right now I don't have any > idea where to begin looking for this. >
simplepack.tar.gz
Description: GNU Zip compressed data
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
