I'm considering for Python 3.4.0a1. The buildbots are all happy,
except for AMD64 Win7 SP1:
http://buildbot.python.org/all/waterfall?category=3.x.stable
The two failures are zipimport and signal. zipimport is sporadic, and
looks like some sort of heisenissue. signal is much more cons
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.
I've got some documentation warnings I can't quash, so I'm not tagging yet.
/
On Sat, Aug 3, 2013 at 2:45 AM, Larry Hastings 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 confus
On 3 August 2013 19:08, Larry Hastings wrote:
>
>
> I'm considering for Python 3.4.0a1. The buildbots are all happy, except
> for AMD64 Win7 SP1:
>
> http://buildbot.python.org/all/waterfall?category=3.x.stable
>
> The two failures are zipimport and signal. zipimport is sporadic, and looks
> li
On 3 August 2013 22:43, Eli Bendersky wrote:
> On Sat, Aug 3, 2013 at 2:45 AM, Larry Hastings 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 i
Quoting Fred Drake :
IT IS HIGHLY RECOMMENDED THAT YOU AT LEAST TAG THE TREE 24 HOURS
BEFORE A FINAL RELEASE. This will give the Experts enough time to
do their bits before the announcement goes out.
The schedule calls for the Alpha 1 release tomorrow. Ergo, tag today.
When I read this, I
Quoting Eli Bendersky :
On Sat, Aug 3, 2013 at 2:45 AM, Larry Hastings 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.
PEP 101 tells me that in order to release Python 3.4.0a1 I must massage
the website. I foolishly left this to the last minute. Can anybody
give me access to the repo and shove me towards the README? Pretty
please? I already have access to dinsdale and am in the "webmaster"
group on there.
In article <[email protected]>,
Larry Hastings wrote:
> PEP 101 tells me that in order to release Python 3.4.0a1 I must massage
> the website. I foolishly left this to the last minute. Can anybody
> give me access to the repo and shove me towards the README?
Shove - website maint
You should already have access to the website repo.
2013/8/3 Larry Hastings :
>
>
> PEP 101 tells me that in order to release Python 3.4.0a1 I must massage the
> website. I foolishly left this to the last minute. Can anybody give me
> access to the repo and shove me towards the README? Pretty p
On behalf of the Python development team, I'm pleased to announce the
first alpha release of Python 3.4.
This is a preview release, and its use is not recommended for
production settings.
Python 3.4 includes a range of improvements of the 3.x series, including
hundreds of small improvements an
All the release engineering work for 3.4.0a1 has been merged. Cry
havoc, and let slip the checkins of war!
//arry/
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
http://www.voodoochilli.net/artwork/illustration/chickens-of-war/
On Aug 4, 2013 4:34 PM, "Larry Hastings" wrote:
>
>
> All the release engineering work for 3.4.0a1 has been merged. Cry havoc,
> and let slip the checkins of war!
>
>
> */arry*
>
> ___
>
On 08/03/2013 11:22 PM, Larry Hastings wrote:
* PEP 435, a standardized "enum" module
* PEP 442, improved semantics for object finalization
* PEP 443, adding single-dispatch generic functions to the standard
library
* PEP 445, a new C API for implementing custom memory allocators
Whoops, look
14 matches
Mail list logo
