On 03/04/2014 03:59 PM, Barry Warsaw wrote:
I too would like an rc3, especially to see if issue 19021 can be fixed, which
I suspect will hit a lot of people.
I talked to the other guys on the 3.4 team, and we're all willing to do
an rc3 this weekend. I'll add that to PEP 429.
In other news
On Mar 05, 2014, at 09:24 AM, Nick Coghlan wrote:
>I think it's also the fact that new feature releases are rare and changes
>of release manager even more so, meaning there's a fair bit of relearning
>involved every time (since what was appropriate a couple of years earlier
>may not be appropriate
On 5 Mar 2014 08:15, "Matthias Klose" wrote:
>
> Am 04.03.2014 15:52, schrieb Brett Cannon:
> > I have also filed http://bugs.python.org/issue20851 to make sure the
> > devguide covers running tests from a tarball. If the way the release has
> > been handled has still bugged you enough it can be d
Am 04.03.2014 15:52, schrieb Brett Cannon:
> I have also filed http://bugs.python.org/issue20851 to make sure the
> devguide covers running tests from a tarball. If the way the release has
> been handled has still bugged you enough it can be discussed at the
> language summit, but it would be the f
On Tue, Mar 4, 2014 at 5:23 AM, Stephen J. Turnbull wrote:
> > Guido van Rossum writes:
>
> > Given that the claim "Python 2 doesn't support Unicode filenames"
> > is factually incorrect (in Python 2.7, most filesystem calls in
> > fact do support Unicode, at least on some platforms),
>
> I
Skip Montanaro wrote:
> I do have one question though. Suppose you encounter a compiler that
> doesn't understand the inline keyword, so you choose the static
> declaration as Kristján suggested. The resulting Python executable
> should be functionally correct, but if the optimizer doesn't happen
On Tue, Mar 4, 2014 at 8:33 AM, Antoine Pitrou wrote:
> On Tue, 04 Mar 2014 11:16:41 +0100
> mar...@v.loewis.de wrote:
> >
> > Quoting Nick Coghlan :
> >
> > > If you don't want to do an rc3 despite the cherry picked changes since
> > > rc2, then you need to make it easy for people to test the ch
On Tue, 04 Mar 2014 11:16:41 +0100
mar...@v.loewis.de wrote:
>
> Quoting Nick Coghlan :
>
> > If you don't want to do an rc3 despite the cherry picked changes since
> > rc2, then you need to make it easy for people to test the changes
> > directly from the release branch. An opaque intermittently
> Guido van Rossum writes:
> Given that the claim "Python 2 doesn't support Unicode filenames"
> is factually incorrect (in Python 2.7, most filesystem calls in
> fact do support Unicode, at least on some platforms),
I don't understand what "support Unicode" means. Just that
with ope
Hi,
2014-03-03 22:38 GMT+01:00 Nick Coghlan :
> Related question - have you decided yet whether or not to do an rc3?
I take a look at current release blocker issues for Python 3.4. I saw
bugfixes (ex: upgrade SQLite from 3.8.3 to 3.8.3.1) but also fixes for
regressions between Python 3.4rc2 and P
On 4 March 2014 20:16, wrote:
>
> Quoting Nick Coghlan :
>
>> If you don't want to do an rc3 despite the cherry picked changes since
>> rc2, then you need to make it easy for people to test the changes
>> directly from the release branch. An opaque intermittently updated
>> tarball is not accepta
Quoting Nick Coghlan :
If you don't want to do an rc3 despite the cherry picked changes since
rc2, then you need to make it easy for people to test the changes
directly from the release branch. An opaque intermittently updated
tarball is not acceptable when none of our infrastructure is designe
12 matches
Mail list logo
