On 03/04/2014 06:46 PM, Larry Hastings wrote:
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
On 5 Mar 2014 12:48, Larry Hastings la...@hastings.org wrote:
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
Le 05/03/2014 03:46, Larry Hastings a écrit :
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
On 6 Mar 2014 01:32, Antoine Pitrou solip...@pitrou.net wrote:
Le 05/03/2014 03:46, Larry Hastings a écrit :
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
Quoting Nick Coghlan ncogh...@gmail.com:
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
On 4 March 2014 20:16, mar...@v.loewis.de wrote:
Quoting Nick Coghlan ncogh...@gmail.com:
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
Hi,
2014-03-03 22:38 GMT+01:00 Nick Coghlan ncogh...@gmail.com:
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
On Tue, 04 Mar 2014 11:16:41 +0100
mar...@v.loewis.de wrote:
Quoting Nick Coghlan ncogh...@gmail.com:
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
On Tue, Mar 4, 2014 at 8:33 AM, Antoine Pitrou solip...@pitrou.net wrote:
On Tue, 04 Mar 2014 11:16:41 +0100
mar...@v.loewis.de wrote:
Quoting Nick Coghlan ncogh...@gmail.com:
If you don't want to do an rc3 despite the cherry picked changes since
rc2, then you need to make it easy
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
On 5 Mar 2014 08:15, Matthias Klose d...@ubuntu.com 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
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 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
Hi,
I would like to know if the cherry-picking rule still applies for
Python 3.4 final? Can I open an issue if I want to see a changeset in
the final version? I'm asking for a typo in tracemalloc documentation:
http://bugs.python.org/issue20814
http://hg.python.org/cpython/rev/a9058b772807
On 03/03/2014 03:01 AM, Victor Stinner wrote:
Hi,
I would like to know if the cherry-picking rule still applies for
Python 3.4 final? Can I open an issue if I want to see a changeset in
the final version?
Sadly, yes.
//arry/
___
Python-Dev mailing
2014-03-03 13:13 GMT+01:00 Larry Hastings la...@hastings.org:
I would like to know if the cherry-picking rule still applies for
Python 3.4 final? Can I open an issue if I want to see a changeset in
the final version?
Sadly, yes.
Ok, I created:
http://bugs.python.org/issue20843
Why do you
On 3/3/2014 7:13 AM, Larry Hastings wrote:
On 03/03/2014 03:01 AM, Victor Stinner wrote:
Hi,
I would like to know if the cherry-picking rule still applies for
Python 3.4 final? Can I open an issue if I want to see a changeset in
the final version?
Sadly, yes.
Doc changes appear online
Am 03.03.2014 19:31, schrieb Terry Reedy:
On 3/3/2014 7:13 AM, Larry Hastings wrote:
On 03/03/2014 03:01 AM, Victor Stinner wrote:
Hi,
I would like to know if the cherry-picking rule still applies for
Python 3.4 final? Can I open an issue if I want to see a changeset in
the final version?
On 03/03/2014 05:05 AM, Victor Stinner wrote:
2014-03-03 13:13 GMT+01:00 Larry Hastings la...@hastings.org:
I would like to know if the cherry-picking rule still applies for
Python 3.4 final? Can I open an issue if I want to see a changeset in
the final version?
Sadly, yes.
Ok, I created:
On 4 Mar 2014 07:32, Larry Hastings la...@hastings.org wrote:
On 03/03/2014 05:05 AM, Victor Stinner wrote:
2014-03-03 13:13 GMT+01:00 Larry Hastings la...@hastings.org:
I would like to know if the cherry-picking rule still applies for
Python 3.4 final? Can I open an issue if I want to see
On 03/03/2014 21:38, Nick Coghlan wrote:
On 4 Mar 2014 07:32, Larry Hastings la...@hastings.org
mailto:la...@hastings.org wrote:
On 03/03/2014 05:05 AM, Victor Stinner wrote:
2014-03-03 13:13 GMT+01:00 Larry Hastings la...@hastings.org
mailto:la...@hastings.org:
I would like to know
On Mar 03, 2014, at 10:36 PM, Mark Lawrence wrote:
Will this impact on the decision http://bugs.python.org/issue20846 ?
Issue 20808 is my own pet cherry pick for 3.4.
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Will this impact on the decision http://bugs.python.org/issue20846 ?
This issue has been closed as wontfix. It has no patch and must be reported
to pip, not python.
Victor
___
Python-Dev mailing list
Python-Dev@python.org
On 4 Mar 2014 08:40, Mark Lawrence breamore...@yahoo.co.uk wrote:
On 03/03/2014 21:38, Nick Coghlan wrote:
On 4 Mar 2014 07:32, Larry Hastings la...@hastings.org
mailto:la...@hastings.org wrote:
On 03/03/2014 05:05 AM, Victor Stinner wrote:
2014-03-03 13:13 GMT+01:00 Larry
On 03/03/2014 01:38 PM, Nick Coghlan wrote:
Related question - have you decided yet whether or not to do an rc3?
I ask, as I believe it would be good to give the folks like Mike Bayer
and Armin Ronacher (who picked up test coverage gaps in rc2 via the
Alembic and Flask test suites
On 4 March 2014 13:35, Larry Hastings la...@hastings.org wrote:
On 03/03/2014 01:38 PM, Nick Coghlan wrote:
Related question - have you decided yet whether or not to do an rc3?
I ask, as I believe it would be good to give the folks like Mike Bayer and
Armin Ronacher (who picked up test
On 03/03/2014 07:58 PM, Nick Coghlan wrote:
All of our development guides for testing against trunk are designed
around running from a Mercurial checkout - it would *really* be whole
lot easier for everyone else that is trying to test the release if you
could just do a push from your release
On 4 March 2014 14:20, Larry Hastings la...@hastings.org wrote:
On 03/03/2014 07:58 PM, Nick Coghlan wrote:
All of our development guides for testing against trunk are designed
around running from a Mercurial checkout - it would *really* be whole
lot easier for everyone else that is trying to
On 03/03/2014 10:23 PM, Nick Coghlan wrote:
But at the moment you're making it
*hard* for people to test the release,
How? How is testing against a tarball fundamentally different from
testing against an hg-cloned repository?
I'm really not buying this.
//arry/
On 4 March 2014 16:50, Larry Hastings la...@hastings.org wrote:
On 03/03/2014 10:23 PM, Nick Coghlan wrote:
But at the moment you're making it
*hard* for people to test the release,
How? How is testing against a tarball fundamentally different from testing
against an hg-cloned
30 matches
Mail list logo
