On Wed, Nov 11, 2009 at 1:18 PM, Nick Coghlan wrote:
> I think I've decided I don't mind either way, so I'm fine with whichever
> approach is easier for Benjamin and the platform installer builders to
> manage.
+1
--
--Guido van Rossum (python.org/~guido)
___
Raymond Hettinger wrote:
>
> [MvL]
>>> I personally think that decoupling the releases would be best, i.e.
>>> not start thinking about 3.2 for another 6 months.
>
> [Benjamin]
>> The problem with that is that there is a period of time where 2.x has
>> features which 3.x doesn't. My preference is
On Tue, Nov 10, 2009 at 10:26 AM, Raymond Hettinger wrote:
>
> [Guido van Rossum]
>>
>> . We used to have releases once a year and
>> we got really big serious feedback from our biggest users that the
>> release cycle was going too fast. We discussed it amply and agreed on
>> a minimum time of 18
[MvL]
I personally think that decoupling the releases would be best, i.e.
not start thinking about 3.2 for another 6 months.
[Benjamin]
The problem with that is that there is a period of time where 2.x has
features which 3.x doesn't. My preference is to move back the whole
schedule 6 months.
Benjamin Peterson wrote:
> 2009/11/10 "Martin v. Löwis" :
>> I personally think that decoupling the releases would be best, i.e.
>> not start thinking about 3.2 for another 6 months.
>
> The problem with that is that there is a period of time where 2.x has
> features which 3.x doesn't. My preferen
2009/11/10 "Martin v. Löwis" :
> I personally think that decoupling the releases would be best, i.e.
> not start thinking about 3.2 for another 6 months.
The problem with that is that there is a period of time where 2.x has
features which 3.x doesn't. My preference is to move back the whole
schedu
Martin v. Löwis wrote:
>>> PEP 3003 states that Python 3.2 will be released 18-24 months after
>>> Python 3.1. Python 3.1 was released on June 2009-06-27 [1], so
>>> theoretically Python 3.2 should be released not before 2010-12-19 [2].
>> The PEP 3003 text isn't allowing for the fact that 3.1 is "
>> PEP 3003 states that Python 3.2 will be released 18-24 months after
>> Python 3.1. Python 3.1 was released on June 2009-06-27 [1], so
>> theoretically Python 3.2 should be released not before 2010-12-19 [2].
>
> The PEP 3003 text isn't allowing for the fact that 3.1 is "3.0 as it
> should have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Raymond Hettinger wrote:
> [Guido van Rossum]
>> . We used to have releases once a year and
>> we got really big serious feedback from our biggest users that the
>> release cycle was going too fast. We discussed it amply and agreed on
>> a minimum time
[Guido van Rossum]
. We used to have releases once a year and
we got really big serious feedback from our biggest users that the
release cycle was going too fast. We discussed it amply and agreed on
a minimum time of 18 months between releases.
If the language moratorium goes into effect, wou
On Tue, Nov 10, 2009 at 8:09 AM, Antoine Pitrou wrote:
> Guido van Rossum python.org> writes:
>>
>> Was this discussed somewhere?
>
> I don't remember so, except for a short subthread on python-ideas where you
> indeed mentioned (to my disappointment :-)) that you were against a one-year
> releas
Guido van Rossum python.org> writes:
>
> Was this discussed somewhere?
I don't remember so, except for a short subthread on python-ideas where you
indeed mentioned (to my disappointment :-)) that you were against a one-year
release period.
Regards
Antoine.
___
On Tue, Nov 10, 2009 at 5:13 AM, Nick Coghlan wrote:
> Arfrever Frehtes Taifersar Arahesis wrote:
>> 2009-11-02 21:00 Benjamin Peterson napisał(a):
>>> I've updated PEP 373 with my proposed release schedule:
>>>
>>> - 2.7/3.2 alpha 1 2009-12-05
>>> - 2.7/3.2 alpha 2 2010-01-09
>>> - 2.7/3.2 alpha
Arfrever Frehtes Taifersar Arahesis wrote:
> 2009-11-02 21:00 Benjamin Peterson napisał(a):
>> I've updated PEP 373 with my proposed release schedule:
>>
>> - 2.7/3.2 alpha 1 2009-12-05
>> - 2.7/3.2 alpha 2 2010-01-09
>> - 2.7/3.2 alpha 3 2010-02-06
>> - 2.7/3.2 alpha 4 2010-03-06
>> - 2.7/3.2 bet
2009-11-02 21:00 Benjamin Peterson napisał(a):
> I've updated PEP 373 with my proposed release schedule:
>
> - 2.7/3.2 alpha 1 2009-12-05
> - 2.7/3.2 alpha 2 2010-01-09
> - 2.7/3.2 alpha 3 2010-02-06
> - 2.7/3.2 alpha 4 2010-03-06
> - 2.7/3.2 beta 1 2010-04-03
> - 2.7/3.2 beta 2 2010-05-01
> - 2.7
15 matches
Mail list logo
