Issue #12 resolved

package required at build time seems to be not fully present at install time?

Hanno Schlichting
created an issue

This is a copy of http://bugs.python.org/setuptools/issue20:

It was confirmed resolved via:

r65949 | phillip.eby | 2008-08-21 20:41:59 +0200 (Thu, 21 Aug 2008) | 2 lines

Candidate fix for http://bugs.python.org/setuptools/issue20

This fix was so far not backported to the 0.6 branch.

Comments (3)

  1. Anonymous

    Wait a minute, if I want to comment on this issue should I use this web page -- http://bitbucket.org/tarek/distribute/issue/12/ -- or http://bugs.python.org/setuptools/issue20 ? I prefer the latter because it is hosted on "python.org" and because it is more likely to be read by other people e.g. PJE. (This is presuming that the issue and the comment is relevant to setuptools, which in this case I believe it is.)

    By the way, a great thing about http://launchpad.net is that it ties together issue tracker entries from multiple issue trackers. If we're going to be using this issue tracker here, hosted on bitbucket.org, then we should probably use launchpad (or something) to cross-link to issues on http://bugs.python.org/setuptools . I can set that up.

    And by the way, I have a comment on this issue. I don't think that the patch fixes the issue, or at least not the whole issue, or at least not all the issues described in http://bugs.python.org/setuptools/issue20 . Of course, without unit tests, who can tell? Maybe we should write unit tests for these issues. I might be able to make some time for that.

  2. Hanno Schlichting reporter

    I think we are not going to be able to sync the two trackers in a fully automated way. We will loose some contributed effort here, which is unfortunate but unavoidable at this point.

    Regarding this issue, I think the original issue was confirmed fixed by the patch that was applied.

    There is a new message in http://bugs.python.org/setuptools/msg235 which seems to hint at a related problem. I'd consider that worth a new issue and not part of this issue itself.

  3. Log in to comment