On 26 January 2014 02:14, Antoine Pitrou solip...@pitrou.net wrote:
On dim., 2014-01-26 at 01:40 +1000, Nick Coghlan wrote:
I think an extra beta is still a good idea, though - I'd like to get
at least the builtins that are already supported converted, since that
clearly demonstrates the
25.01.14 18:14, Antoine Pitrou написав(ла):
I don't think this is a killer feature that would deserve an extension
of the release cycle. The feature freeze period is meant for bug fixing,
not to shoehorn the latest bangs and whistles. Normally the whole Derby
thing should already have waited for
On Sat, Jan 25, 2014 at 3:09 PM, Larry Hastings la...@hastings.org wrote:
To be honest I have absolutely no idea what % of files have been converted
so far. Figuring it out would use time that would be better spent catching
up on my to-do list.
Of the 22 Derby issues:
* 2 have been closed:
On 26 January 2014 22:57, Serhiy Storchaka storch...@gmail.com wrote:
25.01.14 18:14, Antoine Pitrou написав(ла):
I don't think this is a killer feature that would deserve an extension
of the release cycle. The feature freeze period is meant for bug fixing,
not to shoehorn the latest bangs
On 26 January 2014 23:15, Tal Einat talei...@gmail.com wrote:
Having worked intensively on the Derby for over a week, I feel an urge
to see it through soon. The least we could do is to stop adding
features to clinic.py, only fixing bugs; convert everything that is
possible to convert now and
On Sat, 25 Jan 2014 09:35:46 -0800, Eli Bendersky eli...@gmail.com wrote:
On Sat, Jan 25, 2014 at 7:13 AM, R. David Murray rdmur...@bitdance.comwrote:
On Sat, 25 Jan 2014 06:59:19 -0800, Eli Bendersky eli...@gmail.com
wrote:
workplace we had a similar process screwed on top of Jenkins -
For the record, I find the way Openstack does it very awesome, even if
I’m not a huge fan of gerrit itself. It’s also nice that repeated runs make
you file a bug for flaky tests and reference it because you can see which
bugs are causing the most heart ache in the test suite as far as flakiness
Am 25.01.2014 14:09, schrieb Larry Hastings:
I'd like to extend the Derby by two more weeks and add a fourth beta.
In the past I did like the way how accurate the releases were planned and didn't
slip at all, or only slip for a few days.
This may sound a bit selfish, but a few Ubuntu developers
On Jan 25, 2014, at 03:51 PM, Nick Coghlan wrote:
Rather than leaving my ideas undocumented until the language summit in
April, I wrote up what I see as the critical issues in our current
workflow and how I believe Zuul could help us resolve them as a PEP:
http://www.python.org/dev/peps/pep-0462/
On Sun, Jan 26, 2014 at 9:53 AM, Matthias Klose d...@ubuntu.com wrote:
Am 25.01.2014 14:09, schrieb Larry Hastings:
I'd like to extend the Derby by two more weeks and add a fourth beta.
In the past I did like the way how accurate the releases were planned and
didn't
slip at all, or only
On Jan 26, 2014, at 01:59 PM, Eli Bendersky wrote:
This actually sounds like a real and interesting reason to have stable
Python 3.4 out in march. Ubuntu 14.04 is a LTS, which makes it an important
version for corporate distributions.
Ubuntu 14.04 feature freeze is Feb 20, with beta 1 coming on
On Sun, Jan 26, 2014 at 2:16 PM, Barry Warsaw ba...@python.org wrote:
On Jan 26, 2014, at 01:59 PM, Eli Bendersky wrote:
This actually sounds like a real and interesting reason to have stable
Python 3.4 out in march. Ubuntu 14.04 is a LTS, which makes it an
important
version for corporate
On 01/26/2014 02:18 PM, Guido van Rossum wrote:
On Sun, Jan 26, 2014 at 2:16 PM, Barry Warsaw ba...@python.org
mailto:ba...@python.org wrote:
The closer Python 3.4 can stick to the March 16th release, the better.
Yes. That's the whole point of time-based releases. Please stick to
the
On 27 January 2014 02:01, Donald Stufft don...@stufft.io wrote:
For the record, I find the way Openstack does it very awesome, even if
I’m not a huge fan of gerrit itself. It’s also nice that repeated runs make
you file a bug for flaky tests and reference it because you can see which
bugs are
On behalf of the Python development team, I'm quite pleased to announce
the third beta 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
15 matches
Mail list logo