Re: [python-committers] default hg.python.org/cpython is now 3.5

Am 17.03.2014 22:36, schrieb Victor Stinner: > Hi, > > I modified the Misc/NEWS file: > > * I moved 3.3 sections to Misc/HISTORY: items were already present, > but the format in Misc/NEWS was improved (changeset 6ba468d4fa96) > * I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be

Re: [python-committers] default hg.python.org/cpython is now 3.5

On 03/17/2014 04:23 PM, Nick Coghlan wrote: On 18 Mar 2014 07:37, "Victor Stinner" > wrote: > > Hi, > > I modified the Misc/NEWS file: > > * I moved 3.3 sections to Misc/HISTORY: items were already present, > but the format in Misc/NEWS was improved (changeset

Re: [python-committers] default hg.python.org/cpython is now 3.5

On 18 Mar 2014 07:37, "Victor Stinner" wrote: > > Hi, > > I modified the Misc/NEWS file: > > * I moved 3.3 sections to Misc/HISTORY: items were already present, > but the format in Misc/NEWS was improved (changeset 6ba468d4fa96) > * I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already

Re: [python-committers] default hg.python.org/cpython is now 3.5

Hi, I modified the Misc/NEWS file: * I moved 3.3 sections to Misc/HISTORY: items were already present, but the format in Misc/NEWS was improved (changeset 6ba468d4fa96) * I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be present in the 3.4 branch (changeset cb161cd94e6e) Is tha

Re: [python-committers] default hg.python.org/cpython is now 3.5

On 3/17/2014 11:42 AM, Jesus Cea wrote: On 17/03/14 09:51, Victor Stinner wrote: Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only accept security fixes, right? Tradition says that until release *.1 is published. That is, 3.4.1 in this case. According to my memory, b

Re: [python-committers] default hg.python.org/cpython is now 3.5

On 3/17/2014 11:18 AM, Benjamin Peterson wrote: On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote: On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner wrote: Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only accept security fixes, right? Typically we do one last relea

[python-committers] 3.3 branch is now in security fix mode

Hi all, since 3.3.5 and 3.4.0 practically coincided, it is a good point to end the bugfix maintenance of the 3.3 branch. Please only commit security-related fixes to 3.3 from now -- like for 3.2 -- and as always, please set tracker issues that relate to security fixes to "release blocker" priorit

Re: [python-committers] 3.4 buildbots??

Am 17.03.14 16:58, schrieb Jesus Cea: > On 17/03/14 15:16, "Martin v. Löwis" wrote: >> However, I would advise against doing so now, and delay the addition >> of the 3.4 branch until 3.3 is retired from bug fixing, and then >> repurpose all 3.3 configuration for 3.4. Otherwise, some slaves might >>

Re: [python-committers] default hg.python.org/cpython is now 3.5

Am 17.03.2014 17:37, schrieb "Martin v. Löwis": > Am 17.03.14 16:18, schrieb Benjamin Peterson: >> >> >> On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote: >>> On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner >>> wrote: >>> Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2

Re: [python-committers] [Python-Dev] [RELEASED] Python 3.4.0

The what's new looks truly amazing, with pathlib and asyncio being my favourite additions. Thanks for all the hard work. On Mon, Mar 17, 2014 at 5:57 PM, Ryan Gonzalez wrote: > YES!!! +1 to the authors of the statistics and pathlib modules. > > > On Mon, Mar 17, 2014 at 1:29 AM, Larry Hastings

Re: [python-committers] default hg.python.org/cpython is now 3.5

Am 17.03.14 16:18, schrieb Benjamin Peterson: > > > On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote: >> On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner >> wrote: >> >>> Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only >>> accept security fixes, right? >>> >> >> Typical

Re: [python-committers] 3.4 buildbots??

On 17/03/14 15:16, "Martin v. Löwis" wrote: > However, I would advise against doing so now, and delay the addition > of the 3.4 branch until 3.3 is retired from bug fixing, and then > repurpose all 3.3 configuration for 3.4. Otherwise, some slaves might > run out of disk space. Are you actually ta

Re: [python-committers] 3.4 buildbots??

On lun., 2014-03-17 at 09:37 -0500, Zachary Ware wrote: > On Mon, Mar 17, 2014 at 9:16 AM, "Martin v. Löwis" wrote: > > Am 17.03.14 14:52, schrieb Jesus Cea: > >> Do I need to do anything to create the 3.4 branch in the buildbots?. > > > > As a slave operator, you don't need to do anything. As the

Re: [python-committers] default hg.python.org/cpython is now 3.5

On 17/03/14 09:51, Victor Stinner wrote: > Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 > only accept security fixes, right? Tradition says that until release *.1 is published. That is, 3.4.1 in this case. But release manager will tell. -- Jesús Cea Avión

Re: [python-committers] default hg.python.org/cpython is now 3.5

On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote: > On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner > wrote: > > > Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only > > accept security fixes, right? > > > > Typically we do one last release before shutting the last bugf

Re: [python-committers] 3.4 buildbots??

On Mon, Mar 17, 2014 at 9:16 AM, "Martin v. Löwis" wrote: > Am 17.03.14 14:52, schrieb Jesus Cea: >> Do I need to do anything to create the 3.4 branch in the buildbots?. > > As a slave operator, you don't need to do anything. As the master > operator, you would have to edit the configuration file

Re: [python-committers] 3.4 buildbots??

Am 17.03.14 14:52, schrieb Jesus Cea: > Do I need to do anything to create the 3.4 branch in the buildbots?. As a slave operator, you don't need to do anything. As the master operator, you would have to edit the configuration file to add the branch. However, I would advise against doing so now, a

Re: [python-committers] default hg.python.org/cpython is now 3.5

On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner wrote: > Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only > accept security fixes, right? > Typically we do one last release before shutting the last bugfix branch down, but that's Georg's call since 3.3.5 was released so r

[python-committers] 3.4 buildbots??

Do I need to do anything to create the 3.4 branch in the buildbots?. -- Jesús Cea Avión _/_/ _/_/_/_/_/_/ j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ Twitter: @jcea_/_/_/_/ _/_/_/_/_/ jabber / xm

Re: [python-committers] default hg.python.org/cpython is now 3.5

Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only accept security fixes, right? Victor Le 17 mars 2014 07:48, "Larry Hastings" a écrit : > > > The "3.4" branch is now checked in. It contains all the 3.4 releases > since 3.4.0rc1. Its current state is effectively 3.4.1.