p
On 03/03/2016 09:58 AM, Eric Snow wrote:
On Thu, Mar 3, 2016 at 10:39 AM, Brett Cannon wrote:
...what would we need to do to our C API to make
it so that anyone following a new API wouldn't be broken if we dropped the
GIL?
If I recall correctly, this was one key topic that Larry discussed a
olutely don't think we can get rid
of the C API, or even modify it in any meaningful way that would let us
abstract away implementation details like reference counting. As I said
in my original email, this magic wand simply doesn't exist.
//arry/
On 03/05/2016 12:42 AM, Stefan Krah w
ttend, please fill out the form in the next few days! I promise it's
short, clear, and easy. It'll take you only a few minutes, honest.
And remember: if you're a core developer, your invitation is guaranteed,
[BL]arry
On 03/01/2016 05:01 PM, Larry Hastings wrote:
Signups are open
Please sign up today if you want to attend. We want to start planning
the schedule and other details and it really helps to know who's coming
and what they want to talk about as early as possible.
https://us.pycon.org/2016/events/langsummit/
Thanks,
[BL]arry
__
Barry and I have sent out notices to everyone who requested an
invite--check the inbox for the email address you supplied us with!
And boy are our fingers tired,
[BL]arry
___
python-committers mailing list
[email protected]
https://mail
I've been holding off on the hope that one or two bugs would get fixes.
But those seem to have stalled. So I think it's time that we pushed out
a 3.5.2. Maybe announcing a schedule will light a fire under some rumps.
I put "Spring 2016" as the release date for 3.5.2 on the 3.5 release
sc
This month there were over 350 emails in python-dev with the word
"pathlib" in the title. Yet, despite this massive online debate, nobody
volunteered to present about pathlib at the language summit.
Based on Jake Edge's summary of the conversation from LWN.net we've
boiled down the debate
On 04/29/2016 03:53 PM, Guido van Rossum wrote:
The primary debate should be about fspath or not. Inheriting from str
is off the table while I'm BDFL. Removing pathlib from the stdlib
would only be on the table if we can't reach agreement on fspath.
WFM. Are there competing proposals for how
We've sent out notices to all talk submitters telling them whether their
talk was accepted or rejected. If you haven't gotten yours yet, check
your spam folder. If you still can't find it, email us!
See you there,
[BL]arry
___
python-committer
On 06/03/2016 02:50 PM, R. David Murray wrote:
(There are a couple people at the sprints looking
in to it, but the mercurial guys aren't here so we are short on experts).
For future reference: #mercurial on freenode IRC. There's always
someone in there and they're glad to help out with stuf
On 06/06/2016 10:56 AM, Terry Reedy wrote:
I have wondered whether triagers should have a symbol after their name
-- perhaps &.
I smell an assumption of ASCII, when presumably all of Unicode lay open
at our feet.
Let the bikeshedding begin!,
//arry/
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm pleased to announce the availability of
Python 3.4.5rc1 and Python 3.5.2rc1.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. All changes ma
Heads up! This is a courtesy reminder from your friendly 3.4 and 3.5
release manager. Here's a list of all the changes since 3.5.2rc1 that
are currently going into 3.5.2 final:
* 155e665428c6 - Zachary: OpenSSL 1.0.2h build changes for Windows
* cae0b7ffeb9f - Benjamin: fix % in Doc/what
I did ask for a better fix on the bug tracker, about two weeks ago:
http://bugs.python.org/issue26867
But no better fix seems forthcoming. So I'll ship that.
*/arry*
On Fri, Jun 24, 2016 at 2:29 AM, Matthias Klose wrote:
> On 24.06.2016 11:14, Larry Hastings wrote:
> >
&g
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm thrilled to announce the availability of
Python 3.4.5 and Python 3.5.2.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. All changes made t
On 06/27/2016 11:24 AM, R. David Murray wrote:
On Mon, 27 Jun 2016 08:25:40 -0700, Steve Dower wrote:
On 26Jun2016 1932, Larry Hastings wrote:
https://www.python.org/downloads/release/python-352/
...
/p.s. There appears to be a small oops with the Windows installers for
3.5.2--uploaded to the
Here's the release schedule for Python versions 3.5.3 and 3.4.6.
Sun Jan 1st, 2017 - tag 3.5.3rc1and 3.4.6rc1
Mon Jan 2nd, 2017 - release 3.5.3rc1and 3.4.6rc1
Sun Jan 15th, 2017 - tag 3.5.3 finaland 3.4.6final
Mon Jan 16th, 2017 - release 3.5.3 finaland 3.4.6final
The 3.5 branch
Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and
3.4.6 to ship about a month after 3.6.0 did, to "let the dust settle"
around the release. I expect a flood of adoption of 3.6, and people
switching will find bugs, and maybe those bugs are in 3.5 or 3.4. So it
just seemed
100% of votes cast were for "don't slip", so we won't slip.
Retreat! Full steam behind!
//arry/
On 12/20/2016 02:25 AM, Matthias Klose wrote:
On 19.12.2016 06:26, Larry Hastings wrote:
Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and
3.4.6 to ship
Just a reminder: I'll be tagging 3.5.3 rc1 and 3.4.6 rc1 tomorrow, Jan 1
2017, sometime between 24 and 36 hours from now. Please work quickly if
there's anything you need to get in to either of those releases. I'm
hoping that, for once, there are literally no code changes between rc1
and f
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm pleased to announce the availability of
Python 3.4.6rc1 and Python 3.5.6rc1.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 now
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm delighted to announce the availability of
Python 3.4.6 and Python 3.5.3.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 now onl
(reposting, cc'ing python-dev)
It’s that time again: time to start thinking about the Python Language Summit!
The 2017 summit will be held on Wednesday, May 17, from 10am to 4pm, at the
Oregon Convention Center in Portland, Oregon, USA. Your befezzled hosts Larry
and Barry will once again be at
201 - 223 of 223 matches
Mail list logo
