Am 19.02.2014 01:07, schrieb Larry Hastings:
On 02/18/2014 03:54 PM, Victor Stinner wrote:
2014-02-19 0:46 GMT+01:00 Larry Hastings la...@hastings.org:
Is there *any* reason to make this branch public before 3.4.0 final?
I'm a little bit worried by the fact that buildbots will not test it.
Am 19.02.2014 03:46, schrieb Guido van Rossum:
I do think there's one legitimate concern -- someone might pull a diff from
Larry's branch and then accidentally push it back to the public repo, and then
Larry would be in trouble if he was planning to rebase that diff. (The joys of
DVCS -- we
Am 19.02.2014 00:54, schrieb Barry Warsaw:
On Feb 19, 2014, at 12:38 AM, Matthias Klose wrote:
Am 17.02.2014 00:25, schrieb Larry Hastings:
And my local branch will remain private until 3.4.0 final ships!
sorry, but this is so wrong. Is there *any* reason why to keep this branch
private?
On 19 Feb 2014 14:05, Larry Hastings la...@hastings.org wrote:
The URL has changed slightly. Please go here:
http://midwinter.com/~larry/3.4.status/
You'll notice two things:
a merge.status.html file, which shows you the list of revisions that
I've cherry-picked after rc1.
a tarball
Am 19.02.2014 11:04, schrieb Nick Coghlan:
On 19 Feb 2014 14:05, Larry Hastings la...@hastings.org
mailto:la...@hastings.org wrote:
The URL has changed slightly. Please go here:
http://midwinter.com/~larry/3.4.status/
You'll notice two things:
a merge.status.html file, which shows
On Tue, Feb 18, 2014 at 5:10 PM, Mark Lawrence breamore...@yahoo.co.uk wrote:
Sorry if this has already been suggested, but why not introduce a new
singleton to make the database people happier if not happy? To avoid
confusion call it dbnull? A reasonable compromise or complete cobblers? :)
On 19 February 2014 20:09, Georg Brandl g.bra...@gmx.net wrote:
Am 19.02.2014 11:04, schrieb Nick Coghlan:
On 19 Feb 2014 14:05, Larry Hastings la...@hastings.org
mailto:la...@hastings.org wrote:
The URL has changed slightly. Please go here:
http://midwinter.com/~larry/3.4.status/
On Tue, 18 Feb 2014 18:54:23 -0500
Barry Warsaw ba...@python.org wrote:
On Feb 19, 2014, at 12:38 AM, Matthias Klose wrote:
Am 17.02.2014 00:25, schrieb Larry Hastings:
And my local branch will remain private until 3.4.0 final ships!
sorry, but this is so wrong. Is there *any* reason why
On Tue, 18 Feb 2014 18:46:16 -0800
Guido van Rossum gu...@python.org wrote:
I do think there's one legitimate concern -- someone might pull a diff from
Larry's branch and then accidentally push it back to the public repo, and
then Larry would be in trouble if he was planning to rebase that
On Tue, 18 Feb 2014 20:03:31 -0800
Larry Hastings la...@hastings.org wrote:
Only thirty cherry-picked revisions so far. Gosh, you're making my life
easy, guys,
That's a large number of cherry-picked revisions. How many are actually
release-critical?
Regards
Antoine.
On 02/19/2014 01:20 PM, Antoine Pitrou wrote:
On Tue, 18 Feb 2014 18:46:16 -0800
Guido van Rossum gu...@python.org wrote:
I do think there's one legitimate concern -- someone might pull a diff from
Larry's branch and then accidentally push it back to the public repo, and
then Larry would be in
On Wed, Feb 19, 2014 at 1:42 AM, Georg Brandl g.bra...@gmx.net wrote:
Am 19.02.2014 00:54, schrieb Barry Warsaw:
On Feb 19, 2014, at 12:38 AM, Matthias Klose wrote:
Am 17.02.2014 00:25, schrieb Larry Hastings:
And my local branch will remain private until 3.4.0 final ships!
sorry, but
On Feb 19, 2014, at 07:50 AM, Guido van Rossum wrote:
That's why it's RC2 and not 3.4final, right? Once Larry says it's baked,
everyone *will* have a chance to test it. What value is a preview of the
preview really going to add? Give Larry some trust and freedom to do things
in the way that makes
On Wed, Feb 19, 2014 at 4:13 AM, Antoine Pitrou solip...@pitrou.net wrote:
Agreed too. Python isn't developed in private.
That's a ridiculous accusation, bordering on malicious. Larry isn't
developing Python in private. He is simply working on something that
he'll release when he feels
On Wed, Feb 19, 2014 at 8:16 AM, Barry Warsaw ba...@python.org wrote:
On Feb 19, 2014, at 07:50 AM, Guido van Rossum wrote:
That's why it's RC2 and not 3.4final, right? Once Larry says it's baked,
everyone *will* have a chance to test it. What value is a preview of the
preview really going
Am 19.02.2014 16:50, schrieb Guido van Rossum:
On Wed, Feb 19, 2014 at 1:42 AM, Georg Brandl g.bra...@gmx.net
mailto:g.bra...@gmx.net wrote:
Am 19.02.2014 00:54, schrieb Barry Warsaw:
On Feb 19, 2014, at 12:38 AM, Matthias Klose wrote:
Am 17.02.2014 00:25, schrieb Larry
Am 19.02.2014 19:00, schrieb Georg Brandl:
Give Larry some trust and freedom to do things in the way that makes him
comfortable.
I have no doubts that Larry will make 3.4 the best Python yet :) So far he
has discussed most of his procedures with us, so I don't see a reason not to
weigh in
Am 19.02.2014 19:00, schrieb Georg Brandl:
Am 19.02.2014 16:50, schrieb Guido van Rossum:
On Wed, Feb 19, 2014 at 1:42 AM, Georg Brandl g.bra...@gmx.net
mailto:g.bra...@gmx.net wrote:
Am 19.02.2014 00:54, schrieb Barry Warsaw:
On Feb 19, 2014, at 12:38 AM, Matthias Klose wrote:
On 2/19/2014 2:53 AM, Lennart Regebro wrote:
On Tue, Feb 18, 2014 at 5:10 PM, Mark Lawrence breamore...@yahoo.co.uk wrote:
Sorry if this has already been suggested, but why not introduce a new
singleton to make the database people happier if not happy? To avoid
confusion call it dbnull? A
On 20 Feb 2014 04:18, Georg Brandl g.bra...@gmx.net wrote:
Am 19.02.2014 19:00, schrieb Georg Brandl:
Am 19.02.2014 16:50, schrieb Guido van Rossum:
On Wed, Feb 19, 2014 at 1:42 AM, Georg Brandl g.bra...@gmx.net
mailto:g.bra...@gmx.net wrote:
Am 19.02.2014 00:54, schrieb Barry
Apologies if this is misdirected!
I notice the switch to the new python.org web site has happened; but
now PEPs are simply 404:
http://www.python.org/dev/peps/pep-0008/
However, trimming the URL offers a redirect:
http://www.python.org/dev/peps/
-
http://legacy.python.org/dev/peps/
from
On Thu, Feb 20, 2014 at 10:25 AM, Chris Angelico ros...@gmail.com wrote:
I notice the switch to the new python.org web site has happened; but
now PEPs are simply 404:
http://www.python.org/dev/peps/pep-0008/
However, trimming the URL offers a redirect:
http://www.python.org/dev/peps/
-
On 02/19/2014 02:04 AM, Nick Coghlan wrote:
On 19 Feb 2014 14:05, Larry Hastings la...@hastings.org
mailto:la...@hastings.org wrote:
The URL has changed slightly. Please go here:
http://midwinter.com/~larry/3.4.status/
http://midwinter.com/%7Elarry/3.4.status/
You'll notice two
On 02/19/2014 07:20 AM, Yury Selivanov wrote:
About 21 of those are related to asyncio.
On 2/19/2014, 7:42 AM, Antoine Pitrou wrote:
On Tue, 18 Feb 2014 20:03:31 -0800
Larry Hastings la...@hastings.org wrote:
Only thirty cherry-picked revisions so far. Gosh, you're making my
life
easy,
On Wed, Feb 19, 2014 at 4:42 PM, Larry Hastings la...@hastings.org wrote:
Yes, I'm allowing in basically all the asyncio changes, because a)
there's no installed base, and b) Guido is himself very heavily involved in
those changes. It's my opinion that asyncio is going to get a lot of
On 20 February 2014 10:31, Larry Hastings la...@hastings.org wrote:
On 02/19/2014 02:04 AM, Nick Coghlan wrote:
The release is still about a month away. And yes I still plan to go through
the release blockers.
Thanks. I confess I had missed that rc2 - final was already 3 weeks
rather than
Nick Coghlan writes:
I suspect everyone is also highly aware of the fact that there are
some ambitious changes in 3.4,
Which is an argument for longer beta and RC periods than usual, or
maybe some of the ambition should have been restrained. It's not
necessarily a reason why more eyes help
Go to any commit link in hg.python.org/cpython, for example
http://hg.python.org/cpython/rev/d11ca14c9a61.
You have this commit message:
Issue #6815: os.path.expandvars() now supports non-ASCII Unicode
environment variables names and values. [#6815]
The [#6815] link is going to
On Feb 20, 2014, at 10:24 AM, Stephen J. Turnbull wrote:
But should Ubuntu desires be distorting a volunteer RE's process?
Ubuntu 14.04 final freeze is April 10[1], so I think that's the drop dead date
for getting 3.4 final into Ubuntu 14.04. Matthias may correct me, but I think
if we can hit
On 02/19/2014 05:24 PM, Stephen J. Turnbull wrote:
The conflict here is not Larry's
process, it's the decision to make an ambitious release on a short
time schedule. I sympathize with Ubuntu to some extent -- they have a
business to run, after all. But should Ubuntu desires be distorting a
On 20 Feb 2014 12:26, Ethan Furman et...@stoneleaf.us wrote:
On 02/19/2014 05:24 PM, Stephen J. Turnbull wrote:
The conflict here is not Larry's
process, it's the decision to make an ambitious release on a short
time schedule. I sympathize with Ubuntu to some extent -- they have a
On 20/02/14 08:23, Glenn Linderman wrote:
Of course it is not backwards compatible... but once all the database related
None usage is switched to Null usage it should work the same as before,
My problem with this is that there is no clear distinction
between database-related None usage and
On 02/19/2014 05:24 PM, Stephen J. Turnbull wrote:
Nick Coghlan writes:
A user beware, this may be rebased without warning clone would be
fine for that purpose, and I suspect in most cases just running rc2
- final with such a clone available (preserving Larry's current
workflow until
Larry Hastings writes:
Someone could still inadvertently push those revisions back to
trunk, and then we'd have a real mess on our hands. Publishing
tarballs drops the possibility down to about zero.
Note: I see no reason for you to change your process for the 3.4.0
release. I just want
Greg Ewing writes:
Data retrieved from a database is often passed to other code
that has nothing to do with databases, and data received from
other code is inserted into databases. Somewhere in between
someone is going to have to be careful to translate back and
forth between Nones and
In article
CAB+fVUUJgf9gtf_uXk+3sndyp2r++=ELss1iv+So=cuwzje...@mail.gmail.com,
Vajrasky Kok sky@speaklikeaking.com wrote:
Go to any commit link in hg.python.org/cpython, for example
http://hg.python.org/cpython/rev/d11ca14c9a61.
You have this commit message:
Issue #6815:
On 20 February 2014 16:42, Ronald Oussoren ronaldousso...@mac.com wrote:
On 17 Feb 2014, at 00:43, Nick Coghlan ncogh...@gmail.com wrote:
On 17 Feb 2014 08:36, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Larry Hastings wrote:
3) We hold off on merging the rest of the Derby patches
On 20 Feb 2014, at 08:09, Nick Coghlan ncogh...@gmail.com wrote:
On 20 February 2014 16:42, Ronald Oussoren ronaldousso...@mac.com wrote:
On 17 Feb 2014, at 00:43, Nick Coghlan ncogh...@gmail.com wrote:
On 17 Feb 2014 08:36, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Larry
On 17 Feb 2014, at 00:43, Nick Coghlan ncogh...@gmail.com wrote:
On 17 Feb 2014 08:36, Greg Ewing greg.ew...@canterbury.ac.nz wrote:
Larry Hastings wrote:
3) We hold off on merging the rest of the Derby patches until after 3.4.0
final ships, then we merge them into the 3.4
39 matches
Mail list logo
