On Jul 23, 2010, at 6:46 AM, Lennart Regebro wrote:
On Thu, Jul 22, 2010 at 19:10, Gary Poster <gary.poster@canonical.com> wrote:
Well, in that case it probably works now. I'll try again (with the betafix branch, right?)
Yeah, exactly (though like I said, I couldn't dupe it with 1.5.0b1 either)
OK, the way to duplicate it is to run the tests with
$python setup.py test
To make that happen with 1.5.0dev, you have to make an sdist, put that in the trunk directory, and also add
dependency_links = ['.'],
to setup.py parameters.
The error doesn't appear if you run bin/test.
Ah, ok. To my knowledge, these packages don't support that spelling. bin/test is the way to run the tests for the Zope packages AFAIK. Do you, or others, disagree? The fact that you have to modify setup.py in order to run your example seems to support my perspective. If you disagree, I'll see if I can address, but I'd rather not add that to the release blockers if I don't have to.
Although I get other errors when I do that. However, they are not related to your branch, that happens with 1.5.0b2 as well:
Failed example: print system(os.path.join(sample_buildout, 'bin', 'buildout') + ' -q'), Expected nothing Got: install_dir /tmp/tmpa_M-fRbuildoutSetUp/_TEST_/sample-buildout/develop-eggs/tmpDfJdS0build install_dir /tmp/tmpa_M-fRbuildoutSetUp/_TEST_/sample-buildout/develop-eggs/tmpDfNtGFbuild install_dir /tmp/tmpa_M-fRbuildoutSetUp/_TEST_/sample-buildout/develop-eggs/tmpuSWFFvbuild
The install_dir stuff appears to be something that distribute adds. They didn't show up with setuptools. I just made the buildout tests in my betafix branch ignore them. As far as I know, that's a reasonable approach. Gary