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 eli.bendersky
Recipients amaury.forgeotdarc, barry, cvrebert, eli.bendersky, eric.snow, ethan.furman, ezio.melotti, giampaolo.rodola, gvanrossum, ncoghlan, pitrou, rhettinger
Date 2013-08-06.15:31:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
IMHO it's very much dependent on the change. When making C code changes, I usually run the relevant tests with refleaks, and then run the whole test suite; all of this --with-pydebug. Personally I've not encountered cases where non-debug builds failed where debug suceeded for CPython, but for very significant changes I may do some extra runs in the release mode as well (or try to test it on a specific OS). It's very important to watch the bots after committing, because they run a wide variety of configurations you'll be hard pressed to reproduce on your own - so they exercise the change pretty well.
Date User Action Args
2013-08-06 15:31:35eli.benderskysetrecipients: + eli.bendersky, gvanrossum, barry, rhettinger, amaury.forgeotdarc, ncoghlan, pitrou, giampaolo.rodola, ezio.melotti, cvrebert, ethan.furman, eric.snow
2013-08-06 15:31:35eli.benderskysetmessageid: <>
2013-08-06 15:31:35eli.benderskylinkissue18264 messages
2013-08-06 15:31:35eli.benderskycreate