Antoine Pitrou <pit...@free.fr> added the comment: > You've now merged any changes that have come in since you did your thorough > tests, and you're trying to beat the other guy to the push. You want > something that can run *fast* and just proves that the merge didn't hose > Python in some brown paper bag way.
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! 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). 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11651> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
