Tarek Ziadé wrote:
I've been working on a branch of zc.buildout that uses distribute instead of setuptools:
Okay, I now have all but a couple of tests passing on this branch, with all the changes from the trunk merged in as of a few hours ago...
The test failures are a bit weird though:
File "...src/zc/buildout/bootstrap.txt", line 23, in bootstrap.txt Failed example: print 'X'; print system( zc.buildout.easy_install._safe_arg(sys.executable)+' '+ 'bootstrap.py'); print 'X' # doctest: +ELLIPSIS ... Traceback (most recent call last): File "bootstrap.py", line 87, in <module> ws.require('zc.buildout' + VERSION) File ".../distribute-0.6-py2.6.egg/pkg_resources.py", line 621, in require File ".../distribute-0.6-py2.6.egg/pkg_resources.py", line 519, in resolve pkg_resources.DistributionNotFound: setuptools <BLANKLINE>
I can't find where setuptools is being required, any ideas?
The other one seems to be a difference in how buildout signatures are generated:
File "zc.buildout_co/zc.recipe.egg_/src/zc/recipe/egg/api.txt", line 97, in api.txt Failed example: cat(sample_buildout, '.installed.cfg') Expected: ... __buildout_signature__ = sample-6aWMvV2EJ9Ijq+bR8ugArQ== zc.recipe.egg-cAsnudgkduAa/Fd+WJIM6Q== distribute-0.6-py2.4.egg zc.buildout-+rYeCcmFuD1K/aB77XTj5A== ... Got: ... __buildout_signature__ = sample-lpbdfaUB6wBah/5eldWn2w== zc.recipe.egg-EkSb+I3tVPPzlm3QwumIDA== distribute-0.6-py2.6.egg zc.buildout-mUvpjgUjaaBCXzejndcJIA== ...
Again, I'm open to suggestions as to why distribute appears to cause the line endings to vanish in __buildout_signature__?
I'm also curious: do these signatures change with each new version of rc.recipe.egg and distribute get released?
-- Simplistix - Content Management, Batch Processing & Python Consulting