[python-committers] Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?
Eli Bendersky
eliben at gmail.com
Sat Aug 3 14:43:55 CEST 2013
More information about the python-committers mailing list
Sat Aug 3 14:43:55 CEST 2013
- Previous message: [python-committers] Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?
- Next message: [python-committers] Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Aug 3, 2013 at 2:45 AM, Larry Hastings <larry at 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 above is genuine will to understand the release process rather than questioning your reasoning :-) Eli
- Previous message: [python-committers] Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?
- Next message: [python-committers] Tagging 3.4a1 with an unhappy AMD64 Win7 SP1 buildbot?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list