2018-09-25 16:30 GMT-03:00 Yury Selivanov :
> deprecating APIs or behavior. Right now I'm saying "Python 4.0"
> implying that 4.0 will be released right after 3.9.
>
> I've heard multiple opinions on this subject. One of them is that we
> should release 4.0 when we have a major new change, like r
El vie., 28 de sep. de 2018 a la(s) 18:45, Łukasz Langa
(luk...@langa.pl) escribió:
> We'll be enabling GitHub and social logins soon, ideally with adding
> identified committers to the committers group by default. We are looking into
> this right now. In the mean time, please request membership
2008/8/14 Barry Warsaw <[EMAIL PROTECTED]>:
> it would be the developer who committed the broken change. The problem of
> not having access to all the platforms, or not being able to debug problems
> on those platforms is a different issue.
I want to grab a little attention on this issue. It hap
2008/8/14 Brett Cannon <[EMAIL PROTECTED]>:
> But I honestly think this discussion should wait until after we go
> final with 2.6/3.0. Once that happens and we are all not running
Thanks Brett for this. I started to write some responses... and then I
realized I agree with you here, it's better to
2008/8/15 A.M. Kuchling <[EMAIL PROTECTED]>:
> Should we add a 'needsreview' or 'ready-for-review' keyword that could
> be marked on such bugs? People could check for it before diving into
> a bug, and the mythical reviewer could use it too.
*Maybe*. It'd be the fourth keyword there.
But I don'
2008/10/2 Guido van Rossum <[EMAIL PROTECTED]>:
> No need to be sneaky about it, go right ahead. I don't think we should
> retroactively rename rc1 to beta4, but we can certainly label the next
> release as beta5, with an explanation, and the first real release
> candidate should be called rc2 to
2008/10/6 Raymond Hettinger <[EMAIL PROTECTED]>:
>> 15-Oct-2008 3.0 beta 4
>> 05-Nov-2008 3.0 rc 2
>> 19-Nov-2008 3.0 rc 3
>> 03-Dec-2008 3.0 final
>>
>> Given what still needs to be done, is this a reasonable schedule? Do we
>> need two more betas?
>
> Yes to both questions.
I agree with you h
On Thu, Aug 6, 2009 at 8:28 PM, Georg Brandl wrote:
> FWIW, I also think we should make a new micro release right now. We can't
> be seen to take data corruption issues with the most basic file operations
> lightly, especially in Python 3; otherwise, people will think we still don't
> consider it
