This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients alexis, eric.araujo, flox, francismb, higery, jlove, michael.mulich, nadeem.vawda, paul.moore, pitrou, python-dev, rpetrov, tarek, vinay.sajip, westley.martinez
Date 2011-11-12.15:11:19
SpamBayes Score 0.00024685424
Marked as misclassified No
Message-id <1321110680.4.0.982879003872.issue13193@psf.upfronthosting.co.za>
In-reply-to
Content
> That's "should", not "must".
I read that “should” as a polite “must”.

> Also, I thought people did undocumented things with distutils, and we
> had to support these undocumented uses?
People rely on undocumented features and sometimes on bugs.  Thus, we cannot refactor or otherwise clean up internals.  Here, you did change internals.

> I don't see how adding "expected failures" solves anything. [...].
If a buildbot is red for a week because of me and another developer commits something that creates another test failure, they won’t see that a buildbot has turned red because it already was.  It’s just a temporary edition to avoid polluting the buildbots output.

> A "commit adding problem" should be fixed or reverted
The point is that fixing it may take tome.  Reverting is fine by me.
History
Date User Action Args
2011-11-12 15:11:20eric.araujosetrecipients: + eric.araujo, paul.moore, vinay.sajip, pitrou, nadeem.vawda, tarek, rpetrov, flox, alexis, michael.mulich, westley.martinez, python-dev, jlove, higery, francismb
2011-11-12 15:11:20eric.araujosetmessageid: <1321110680.4.0.982879003872.issue13193@psf.upfronthosting.co.za>
2011-11-12 15:11:19eric.araujolinkissue13193 messages
2011-11-12 15:11:19eric.araujocreate