Not quite a drop-in replacement

Issue #164 open
Dave Abrahams
created an issue

[[|This test log]] demonstrates that using


to initialize a virtualenv is not quite equivalent to using an up-to-date setuptools. I'm not really sure what's going on here, but thought you might want to investigate.

To get the necessary sources, clone [[|this repository]], e.g.:

{{{git clone git://}}}

to run the tests and see them work, run {{{python -v -x}}} from the {{{tests/}}} subdirectory. That method uses setuptools==0.6c11. To run the tests with Distribute substituted for setuptools, also pass the {{{--distribute}}} flag to {{{}}}.

Comments (7)

  1. Zooko O'Whielacronx

    Hi there David Abrahams. Thanks for the bug report! I looked at this ticket with the intent of making the title of it more specific, but now I'm not sure what the actual problem is. Can you tell us more specifically what Distribute seems to be doing wrong that Setuptools is doing right, in this test? Thanks!

  2. Dave Abrahams reporter

    Hi Zooko! It's not a question of Setuptools doing anything right or wrong, because Setuptools doesn't promise to be a drop-in replacement for anything. Distribute, on the other hand, promises to be a drop-in replacement for Setuptools, and yet these tests fail completely when Distribute is used that way.

    [The branch cited in the original version of this bug report doesn't exist anymore, so I updated the instructions for reproducing the problem above.]

  3. Anonymous
  4. Log in to comment