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 barry
Recipients barry, nadeem.vawda, ncoghlan, pitrou
Date 2011-03-23.17:01:47
SpamBayes Score 5.1409654e-07
Marked as misclassified No
Message-id <20110323130139.60d04640@neurotica.wooz.org>
In-reply-to <1300897373.3495.19.camel@localhost.localdomain>
Content
On Mar 23, 2011, at 04:22 PM, Antoine Pitrou wrote:

>What does "brown paper bag way" mean? It seems to be some kind of urban
>legend at this point. A merge won't magically break all C files and
>prevent Python from compiling. Especially if no C files were touched in
>the first place!

This whole thread came up originally because some folks wanted a smoke test
while resolving the merge race window.

>If you are confident that you didn't introduce any issue then just
>commit your merge and push (or run the tests which are relevant to your
>initial commit).

A smoke test addresses the confidence issue, while not introducing a longer
race window to run the full test suite.

>Oh, and again, if some tests are slow on your system, then *please* open
>issues about them (and/or investigate *why* they are slow). That's much
>better than ignoring/blacklisting them.

Sure.
History
Date User Action Args
2011-03-23 17:01:47barrysetrecipients: + barry, ncoghlan, pitrou, nadeem.vawda
2011-03-23 17:01:47barrylinkissue11651 messages
2011-03-23 17:01:47barrycreate