On 3 August 2013 22:43, Eli Bendersky <eli...@gmail.com> wrote: > On Sat, Aug 3, 2013 at 2:45 AM, Larry Hastings <la...@hastings.org> wrote: >> On 08/03/2013 02:08 AM, Larry Hastings wrote: >> >> Can we, uh, live with that, for alpha 1? >> >> >> Ned pointed out, signal and zipimport worked on the retry. So it's >> sporadic, whatever it is. I think we can live with that. >> > > This is confusing. Why do we need an alpha release in the first place? > Is it more important to make it on the exact day than to have a more > functional release? Assuming that 64-bit Windows 7 is the most popular > (or close to it) Windows out there today, that sounds like an annoying > flaw.
The test_signal problem was just a conflict between the details of the test and having faulthandler enabled. Nothing wrong with the signal handling itself. > The above is genuine will to understand the release process rather > than questioning your reasoning :-) Alpha deadlines are the ones with the *least* excuses for delays. It's better to expose the 99.9% that is working for broader feedback rather than holding that side of the process up for a couple of minor flaws. The trade-offs change as you move closer to a final release, but this early in the cycle erring on the side of "just ship it" is a good way to go. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
