Hello all,
As with previous years we will be having a Language Summit at PyCon North
America, in Montreal. The summit will be on Wednesday 9th April and running
from approximately 10am to 4pm.
As Python committers you're invited, but please respond if you're attending so
I can track numbers. W
Summit topic: when are we going to sunset Python 2.7?
On Wed, Dec 4, 2013 at 7:22 AM, Michael Foord wrote:
> Hello all,
>
> As with previous years we will be having a Language Summit at PyCon North
> America, in Montreal. The summit will be on Wednesday 9th April and running
> from approximately
On Wed, Dec 4, 2013 at 6:26 AM, Brett Cannon wrote:
> Summit topic: when are we going to sunset Python 2.7?
>
>
Define "sunset" :)
Eli
>
> On Wed, Dec 4, 2013 at 7:22 AM, Michael Foord wrote:
>
>> Hello all,
>>
>> As with previous years we will be having a Language Summit at PyCon North
>> Ame
On mer., 2013-12-04 at 09:11 -0800, Eli Bendersky wrote:
>
>
>
> On Wed, Dec 4, 2013 at 6:26 AM, Brett Cannon wrote:
> Summit topic: when are we going to sunset Python 2.7?
>
>
>
>
> Define "sunset" :)
A romantic evening with the bsddb module perhaps?
Then we tie i
On Wed, Dec 4, 2013 at 12:11 PM, Eli Bendersky wrote:
>
>
>
> On Wed, Dec 4, 2013 at 6:26 AM, Brett Cannon wrote:
>
>> Summit topic: when are we going to sunset Python 2.7?
>>
>>
> Define "sunset" :)
>
Stop supporting/EOL.
-Brett
>
> Eli
>
>
>>
>> On Wed, Dec 4, 2013 at 7:22 AM, Michael Foor
On 4 Dec 2013, at 14:26, Brett Cannon wrote:
> Summit topic: when are we going to sunset Python 2.7?
>
I've added it to the agenda with your name...
Thanks,
Michael
>
> On Wed, Dec 4, 2013 at 7:22 AM, Michael Foord
> wrote:
> Hello all,
>
> As with previous years we will be having a La
On Wed, Dec 4, 2013 at 12:46 PM, Michael Foord wrote:
>
> On 4 Dec 2013, at 14:26, Brett Cannon wrote:
>
> > Summit topic: when are we going to sunset Python 2.7?
> >
>
> I've added it to the agenda with your name...
>
As my name is being attached to a discussion of ending the development of
Pyt
On 4 Dec 2013, at 17:48, Brett Cannon wrote:
>
>
>
> On Wed, Dec 4, 2013 at 12:46 PM, Michael Foord
> wrote:
>
> On 4 Dec 2013, at 14:26, Brett Cannon wrote:
>
> > Summit topic: when are we going to sunset Python 2.7?
> >
>
> I've added it to the agenda with your name...
>
> As my name
On 4 Dec 2013, at 18:01, Zachary Ware wrote:
> On Wed, Dec 4, 2013 at 6:22 AM, Michael Foord
> wrote:
>> Hello all,
>>
>> As with previous years we will be having a Language Summit at PyCon North
>> America, in Montreal. The summit will be on Wednesday 9th April and running
>> from approxim
On Wed, Dec 4, 2013 at 6:22 AM, Michael Foord wrote:
> Hello all,
>
> As with previous years we will be having a Language Summit at PyCon North
> America, in Montreal. The summit will be on Wednesday 9th April and running
> from approximately 10am to 4pm.
>
> As Python committers you're invited,
Am 04.12.2013 19:01, schrieb Michael Foord:
>> I've added it to the agenda with your name...
>>
>> As my name is being attached to a discussion of ending the
>> development of Python 2, will there be a place for people to
>> check their pitchforks at the door? =)
>>
>
> On the contrary, I think
On 4 Dec 2013, at 18:13, Christian Heimes wrote:
> Am 04.12.2013 19:01, schrieb Michael Foord:
>>> I've added it to the agenda with your name...
>>>
>>> As my name is being attached to a discussion of ending the
>>> development of Python 2, will there be a place for people to
>>> check their pi
On mer., 2013-12-04 at 18:19 +0100, Antoine Pitrou wrote:
> On mer., 2013-12-04 at 09:11 -0800, Eli Bendersky wrote:
> >
> >
> >
> > On Wed, Dec 4, 2013 at 6:26 AM, Brett Cannon wrote:
> > Summit topic: when are we going to sunset Python 2.7?
> >
> >
> >
> >
> > Defi
Am 04.12.2013 19:14, schrieb Michael Foord:
>
> On 4 Dec 2013, at 18:13, Christian Heimes
> wrote:
>
>> Am 04.12.2013 19:01, schrieb Michael Foord:
I've added it to the agenda with your name...
As my name is being attached to a discussion of ending the
development of Python
On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wrote:
>As for the question, I think we should wait at least two or three years
>before "sunsetting" 2.7.
I've been thinking we should move Python 2.7 to security-fix only around the
Python 3.5 time frame, with a couple more years of promised security
2013/12/4 Barry Warsaw :
> On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wrote:
>
>>As for the question, I think we should wait at least two or three years
>>before "sunsetting" 2.7.
>
> I've been thinking we should move Python 2.7 to security-fix only around the
> Python 3.5 time frame, with a coup
On 04.12.2013 20:07, Benjamin Peterson wrote:
> 2013/12/4 Barry Warsaw :
>> On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wrote:
>>
>>> As for the question, I think we should wait at least two or three years
>>> before "sunsetting" 2.7.
>>
>> I've been thinking we should move Python 2.7 to security-
On Wed, Dec 4, 2013 at 11:47 AM, M.-A. Lemburg wrote:
> On 04.12.2013 20:07, Benjamin Peterson wrote:
> > 2013/12/4 Barry Warsaw :
> >> On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wrote:
> >>
> >>> As for the question, I think we should wait at least two or three years
> >>> before "sunsetting"
On 04.12.2013 21:28, Eli Bendersky wrote:
> On Wed, Dec 4, 2013 at 11:47 AM, M.-A. Lemburg wrote:
>
>> On 04.12.2013 20:07, Benjamin Peterson wrote:
>>> 2013/12/4 Barry Warsaw :
On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wrote:
> As for the question, I think we should wait at leas
Am 04.12.2013 20:07, schrieb Benjamin Peterson:
> FWIW, the current plan is to have the last normal release in 2015
> and security releases "indefinitely" (2020 or something like
> that).
Can we make an exception for platform support, e.g. compatibility
fixes with new compiler or library versions?
2013/12/4 Christian Heimes :
> Am 04.12.2013 20:07, schrieb Benjamin Peterson:
>> FWIW, the current plan is to have the last normal release in 2015
>> and security releases "indefinitely" (2020 or something like
>> that).
>
> Can we make an exception for platform support, e.g. compatibility
> fixes
On Wed, 2013-12-04 at 12:28 -0800, Eli Bendersky wrote:
>
>
>
> On Wed, Dec 4, 2013 at 11:47 AM, M.-A. Lemburg wrote:
> On 04.12.2013 20:07, Benjamin Peterson wrote:
> > 2013/12/4 Barry Warsaw :
> >> On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wrote:
> >>
>
On Wed, Dec 4, 2013 at 2:47 PM, M.-A. Lemburg wrote:
> On 04.12.2013 21:28, Eli Bendersky wrote:
> > On Wed, Dec 4, 2013 at 11:47 AM, M.-A. Lemburg wrote:
> >
> >> On 04.12.2013 20:07, Benjamin Peterson wrote:
> >>> 2013/12/4 Barry Warsaw :
> On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wro
On 05.12.2013 00:03, Brian Curtin wrote:
> On Wed, Dec 4, 2013 at 2:47 PM, M.-A. Lemburg wrote:
>>> Can you clarify on some specific interesting cases you ran into?
>>
>> One example is users stuck on e.g. Zope 2.10 or Plone 3.3 (or even
>> earlier). They cannot upgrade because they are using cust
On 5 Dec 2013 09:04, "Brian Curtin" wrote:
>
> On Wed, Dec 4, 2013 at 2:47 PM, M.-A. Lemburg wrote:
>>
>> On 04.12.2013 21:28, Eli Bendersky wrote:
>> > On Wed, Dec 4, 2013 at 11:47 AM, M.-A. Lemburg wrote:
>> >
>> >> On 04.12.2013 20:07, Benjamin Peterson wrote:
>> >>> 2013/12/4 Barry Warsaw :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/12/13 18:19, Antoine Pitrou wrote:
>> Define "sunset" :)
>
> A romantic evening with the bsddb module perhaps? Then we tie it to
> a weakref and throw it in the ocean.
bsddb, Glup! :-).
I can't attend the summit, but I would like to discuss DT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/12/13 00:22, M.-A. Lemburg wrote:
> Like many other systems, Zope and Plone only support a few Python
> versions for each release. If you want to upgrade to later Python
> versions, you have to upgrade to newer Zope and Plone versions as
> well.
27 matches
Mail list logo
