Am 04.10.2012 um 03:38 schrieb R. David Murray rdmur...@bitdance.com:
Other proposed large-scale changes:
[...]
* A standard event-loop interface (PEP by Jim Fulton pending)
Really? Was this discussed somewhere? I'd like to know more about it.
I believe it was discussed at the Language
Am 03.10.2012 13:54, schrieb Larry Hastings:
As for the rest of it, my understanding was that there is no longer any
great plan written in the stars for Python releases. Python releases
are comprised of whatever features people propose, implement, and are
willing to support, that they can get
On Thu, Oct 4, 2012 at 12:32 PM, Christian Heimes christ...@python.org wrote:
Two days ago NIST announced the SHA-3 contest winner. My wrapper of
keccak https://bitbucket.org/tiran/pykeccak/ is almost ready and just
needs some cleanup and more tests. Once it's done I'll remove the Python
3.2
Am 04.10.2012 12:49, schrieb Dirkjan Ochtman:
On Thu, Oct 4, 2012 at 12:32 PM, Christian Heimes christ...@python.org
wrote:
Two days ago NIST announced the SHA-3 contest winner. My wrapper of
keccak https://bitbucket.org/tiran/pykeccak/ is almost ready and just
needs some cleanup and more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/12 17:27, Nick Coghlan wrote:
I received a fair number of complaints from people that wanted to
experiment with yield from, but couldn't, because the first alpha
wasn't out yet and they weren't sufficiently interested to go to
the
Hello :)
That PEP is indeed pining to the fjords. I may be able to contribute (and
hopefully I can with the preliminary research and
talking-to-people-about-what-they-want that I've already done that maybe
hasn't made it into the draft PEP versions), but I can not currently spare
the cycles to
On 03.10.12 20:10, MRAB wrote:
I downloaded the alphas to test the support for PEP 393 I'd added to
the regex module.
Hardly alpha would be useful to you if it released before PEP 393
implementation.
___
Python-Dev mailing list
mar...@v.loewis.de writes:
We once had nightly builds of the Windows installers. It required a
dedicated buildbot operator, since the process tended to break.
For what it's worth, I'd be willing to try to re-institute the daily
Windows installer builds if they'd see usage, but I suspect I'll
On 10/3/2012 12:02 PM, Larry Hastings wrote:
What it really comes down to: I'm a first-time RM, and I lack the
courage/wisdom to overrule what appears to be a reasonable status quo.
I feel I don't have to defend the decision to maintain the status quo; I
feel instead you have to make a case for
In article
20121003203328.horde.za5_tqgzi1vqbit43mhb...@webmail.df.eu,
mar...@v.loewis.de wrote:
I wouldn't mind having alpha 1 in April 2013, and alpha 2 in October 2013.
I share Larry's skepticism, and actually fear that it may confuse users
(which find that they test something completely
Executive summary:
Larry admits that doing an early alpha is a plausible experiment, he
just has reasons not to do it himself. OTOH, Nick has a reason for
wanting to do it in *this* release cycle.
It's Larry's call; we should restrict ourselves to giving him the
information he requests to make
Howdy howdy. Unless someone has a better idea, I'm the release manager
for Python 3.4. I've roughed out a release schedule, assuming a
16-month period between 3.3 and 3.4. It works out to having 3.4 ship
about seven weeks before the PyCon 2014 core dev sprint, so even if we
slip some we
On Wed, Oct 3, 2012 at 4:57 PM, Larry Hastings la...@hastings.org wrote:
Howdy howdy. Unless someone has a better idea, I'm the release manager for
Python 3.4. I've roughed out a release schedule, assuming a 16-month period
between 3.3 and 3.4. It works out to having 3.4 ship about seven
I've roughed out a release schedule
Is there a rough list of changes for 3.4 written down somewhere, or is
that only to be inferred based on PEPs whose Python-Version header
reads 3.4? How confident are you that the schedule you've proposed
gives enough time for proposed changes to be
On 10/03/2012 01:40 PM, Nick Coghlan wrote:
On Wed, Oct 3, 2012 at 4:57 PM, Larry Hastings la...@hastings.org wrote:
- 3.4.0 alpha 1: August 3, 2013
Looks pretty good to me, but I'd still like to experiment with
bringing this one up a few months (say to April, a few weeks after
PyCon US 2013).
On 10/03/2012 01:45 PM, Skip Montanaro wrote:
Is there a rough list of changes for 3.4 written down somewhere, or is
that only to be inferred based on PEPs whose Python-Version header
reads 3.4? How confident are you that the schedule you've proposed
gives enough time for proposed changes to
On 10/03/2012 01:54 PM, Larry Hastings wrote:
On 10/03/2012 01:45 PM, Skip Montanaro wrote:
Is there a rough list of changes for 3.4 written down somewhere, or is that
only to be inferred based on PEPs whose Python-Version header reads 3.4? How
confident are you that the schedule you've
On Oct 03, 2012, at 06:45 AM, Skip Montanaro wrote:
Is there a rough list of changes for 3.4 written down somewhere
Let the wild rumpus begin!
-Barry
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
On Wed, Oct 3, 2012 at 5:16 PM, Larry Hastings la...@hastings.org wrote:
I don't agree. It's my understanding that the alphas are largely ignored,
and having them earlier would hardly make them more relevant.
I would appreciate it you stopped promoting this myth. Each step in
the release
On 10/03/2012 04:55 PM, Nick Coghlan wrote:
Regardless of when the first alpha happens, I'll be promoting the hell
out of it, begging for feedback on any of these changes that are
available by then (which should be quite a few, given the preceding
PyCon US sprints).
If you can show me people
If you can show me people who use the alphas who want them earlier, I'll
consider it. So far the only person who's said they want them is you, and
IIUC you won't be a consumer of the alpha per se.
Begging for feedback doesn't mean you'll get any,
I haven't done any Python core development
On Wed, 03 Oct 2012 20:25:17 +0530, Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Oct 3, 2012 at 5:16 PM, Larry Hastings la...@hastings.org wrote:
I don't agree. It's my understanding that the alphas are largely ignored,
and having them earlier would hardly make them more relevant.
I
On Wed, Oct 3, 2012 at 8:43 PM, Larry Hastings la...@hastings.org wrote:
Begging for feedback doesn't mean you'll get any,
I received a fair number of complaints from people that wanted to
experiment with yield from, but couldn't, because the first alpha
wasn't out yet and they weren't
On Wed, Oct 3, 2012 at 5:27 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Oct 3, 2012 at 8:43 PM, Larry Hastings la...@hastings.org wrote:
Begging for feedback doesn't mean you'll get any,
I received a fair number of complaints from people that wanted to
experiment with yield from, but
On Wed, Oct 3, 2012 at 10:13 AM, Larry Hastings la...@hastings.org wrote:
On 10/03/2012 04:55 PM, Nick Coghlan wrote:
Regardless of when the first alpha happens, I'll be promoting the hell
out of it, begging for feedback on any of these changes that are
available by then (which should be
On Wed, Oct 3, 2012 at 8:58 PM, Brian Curtin br...@python.org wrote:
This doesn't answer the question of the users wanting the alphas
earlier, but they're certainly more than largely ignored...
The webstats in April 2012 show 5628 downloads of 3.3a1 and 4946
downloads of 3.3a2 Windows
On Wed, Oct 3, 2012 at 8:59 PM, Maciej Fijalkowski fij...@gmail.com wrote:
On Wed, Oct 3, 2012 at 5:27 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Oct 3, 2012 at 8:43 PM, Larry Hastings la...@hastings.org wrote:
Begging for feedback doesn't mean you'll get any,
I received a fair number
On Wed, Oct 3, 2012 at 8:55 AM, Nick Coghlan ncogh...@gmail.com wrote:
I *can't* effectively trial
those changes on PyPI (except perhaps some of the disassembly
changes), and I don't have the resources to create and distribute
Windows and Mac OS X installers on my own. That means, before the
On 3 October 2012 16:13, Larry Hastings la...@hastings.org wrote:
On 10/03/2012 04:55 PM, Nick Coghlan wrote:
Regardless of when the first alpha happens, I'll be promoting the hell
out of it, begging for feedback on any of these changes that are
available by then (which should be quite a few,
On Oct 03, 2012, at 11:22 AM, R. David Murray wrote:
I don't have any data to back this up, but it is my impression that more
distributions are providing access to alpha releases in their testing
package trees.
Ubuntu and Debian generally does, thanks to Matthias's great work. Python
3.3's been
On 10/03/2012 05:27 PM, Nick Coghlan wrote:
That's your prerogative as RM of course, but you haven't given any
reason beyond the circular I don't care about enabling feedback from
people that can't or won't build from source, because people that
can't or won't build from source don't provide
On Wed, Oct 3, 2012 at 11:02 AM, Larry Hastings la...@hastings.org wrote:
On 10/03/2012 05:28 PM, Brian Curtin wrote:
The webstats in April 2012 show 5628 downloads of 3.3a1 and 4946
downloads of 3.3a2 Windows installers.
I'd love to know how much feedback we got as a result of these
Nick Coghlan writes:
I proposed to Larry originally that we start the alphas 6 months
after 3.3.0,
I like this idea better, even though to keep the total workload
constant you'd need to more than double the interval between alphas.
Still, a 10- or 12-month release schedule feels like a much
On Wed, 03 Oct 2012 18:02:03 +0200, Larry Hastings la...@hastings.org wrote:
Changing an existing alpha to be earlier doesn't alter the workload, but
I fear it makes the alpha less relevant. Evaluating alphas / betas
takes an investment of time, and whether or not a potential alpha user
On Wed, 03 Oct 2012 11:19:57 -0500, Brian Curtin br...@python.org wrote:
On Wed, Oct 3, 2012 at 11:02 AM, Larry Hastings la...@hastings.org wrote:
On 10/03/2012 05:28 PM, Brian Curtin wrote:
The webstats in April 2012 show 5628 downloads of 3.3a1 and 4946
downloads of 3.3a2 Windows
Nick Coghlan wrote:
On Wed, Oct 3, 2012 at 8:58 PM, Brian Curtin br...@python.org wrote:
This doesn't answer the question of the users wanting the alphas
earlier, but they're certainly more than largely ignored...
The webstats in April 2012 show 5628 downloads of 3.3a1 and 4946
downloads of
On 3 October 2012 17:34, R. David Murray rdmur...@bitdance.com wrote:
There *were* bug reports during the alpha phase. A number of regressions
were caught. Also, there were more alpha-phase bug reports than
I remember getting for 3.2. I remember thinking, wow, cool, we're
actually getting
On 03.10.12 19:02, Larry Hastings wrote:
But my suspicion is that most people who
try the alphas are doing early integration testing with their own
stuff. For those people, the earlier the alpha, the less interesting it
probably is to them. Earlier means that the software will be less
finished.
On 10/03/2012 06:26 PM, R. David Murray wrote:
On Wed, 03 Oct 2012 18:02:03 +0200, Larry Hastings la...@hastings.org wrote:
Changing an existing alpha to be earlier doesn't alter the workload, but
I fear it makes the alpha less relevant. Evaluating alphas / betas
takes an investment of time,
On 2012-10-03 16:28, Brian Curtin wrote:
On Wed, Oct 3, 2012 at 10:13 AM, Larry Hastings la...@hastings.org wrote:
On 10/03/2012 04:55 PM, Nick Coghlan wrote:
Regardless of when the first alpha happens, I'll be promoting the hell
out of it, begging for feedback on any of these changes that are
On Wed, 3 Oct 2012 20:05:24 +0200
Antoine Pitrou solip...@pitrou.net wrote:
On Wed, 3 Oct 2012 20:25:17 +0530
Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Oct 3, 2012 at 5:16 PM, Larry Hastings la...@hastings.org wrote:
I don't agree. It's my understanding that the alphas are largely
Zitat von Larry Hastings la...@hastings.org:
I welcome your feedback--without any further input I'll go ahead and
post this as a PEP in a week or so.
I personally feel that the release period is too long. Is it really necessary
to start with the release more than 6 month before the
Zitat von Skip Montanaro s...@pobox.com:
I've roughed out a release schedule
Is there a rough list of changes for 3.4 written down somewhere, or is
that only to be inferred based on PEPs whose Python-Version header
reads 3.4? How confident are you that the schedule you've proposed
gives
Zitat von Eric Snow ericsnowcurren...@gmail.com:
On Wed, Oct 3, 2012 at 8:55 AM, Nick Coghlan ncogh...@gmail.com wrote:
I *can't* effectively trial
those changes on PyPI (except perhaps some of the disassembly
changes), and I don't have the resources to create and distribute
Windows and Mac
Zitat von Maciej Fijalkowski fij...@gmail.com:
On Wed, Oct 3, 2012 at 5:27 PM, Nick Coghlan ncogh...@gmail.com wrote:
On Wed, Oct 3, 2012 at 8:43 PM, Larry Hastings la...@hastings.org wrote:
Begging for feedback doesn't mean you'll get any,
I received a fair number of complaints from
Zitat von Nick Coghlan ncogh...@gmail.com:
Regardless of when the first alpha happens, I'll be promoting the hell
out of it, begging for feedback on any of these changes that are
available by then (which should be quite a few, given the preceding
PyCon US sprints). However, I would *like* to
2012/10/3 Larry Hastings la...@hastings.org:
Other proposed large-scale changes:
[...]
* A standard event-loop interface (PEP by Jim Fulton pending)
Really? Was this discussed somewhere? I'd like to know more about it.
--- Giampaolo
http://code.google.com/p/pyftpdlib/
On Thu, 04 Oct 2012 03:14:11 +0200, =?ISO-8859-1?Q?Giampaolo_Rodol=E0?=
g.rod...@gmail.com wrote:
2012/10/3 Larry Hastings la...@hastings.org:
Other proposed large-scale changes:
[...]
* A standard event-loop interface (PEP by Jim Fulton pending)
Really? Was this discussed somewhere?
mar...@v.loewis.de writes:
I wouldn't mind having alpha 1 in April 2013, and alpha 2 in October 2013.
I share Larry's skepticism, and actually fear that it may confuse users
(which find that they test something completely different from what gets
released).
I don't really think you need
49 matches
Mail list logo
