Re: [Python-Dev] Released: Python 2.6.9 release candidate 1

Ooh！ths! 2013/10/1 Barry Warsaw > Hello Pythoneers and Pythonistas, > > I'm happy to announce the availability of Python 2.6.9 release candidate 1. > > Python 2.6.9rc1 is a security-fix source-only release for Python 2.6. This > means that general bug maintenance has ended, and

[Python-Dev] Released: Python 2.6.9 release candidate 1

Hello Pythoneers and Pythonistas, I'm happy to announce the availability of Python 2.6.9 release candidate 1. Python 2.6.9rc1 is a security-fix source-only release for Python 2.6. This means that general bug maintenance has ended, and only critical security issues are being fixed. It also means

[Python-Dev] Python for new users

Nick Efford writes: > Widely-used and linked web resources tend to persist for a very > long time, so we shouldn't use the prevalence of Python 2 resources > as a reason for excessive caution. The key question is how much > good material is available based on Python 3 - and this has improved

Re: [Python-Dev] peps: document requirements

Am 30.09.2013 20:16, schrieb Antoine Pitrou: > On Mon, 30 Sep 2013 17:08:00 +0200 (CEST) > christian.heimes wrote: >> + >> +* It should return ``0`` for zero length input. (Note: This can be handled >> as >> + special case, too.) > > What is this required for? The main requirement is that equal

Re: [Python-Dev] peps: document requirements

On Mon, 30 Sep 2013 17:08:00 +0200 (CEST) christian.heimes wrote: > + > +* It should return ``0`` for zero length input. (Note: This can be handled as > + special case, too.) What is this required for? The main requirement is that equal stuff hashes equal, but there's no reason for zero-length i

Re: [Python-Dev] cpython (2.7): Add fake buildbottouch target.

On Mon, 30 Sep 2013 16:18:57 +0200 (CEST) martin.v.loewis wrote: > http://hg.python.org/cpython/rev/c1a294bbb4fa > changeset: 85882:c1a294bbb4fa > branch: 2.7 > parent: 85877:dd55d54b2a15 > user:Martin v. Löwis > date:Mon Sep 30 16:18:31 2013 +0200 > summary: > Add f

Re: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio

On 09/29/2013 08:55 PM, Guido van Rossum wrote: > On Sun, Sep 29, 2013 at 5:40 PM, Eric V. Smith > wrote: > > On 9/27/2013 9:14 PM, Brett Cannon wrote: > > > I don't see any issue with redirecting the discussion. > python-tulip@ is > > acting like a SIG

[Python-Dev] Python for new users

In the 'PEP453 ready for pronouncement' thread, Donald said Because reality is that new users are still likely to be using Python 2.7. Python 3 is just now starting to be really usable, however there's a huge corpus of existing tutorials, course work, books etc for Python 2.7. As Python 3 become

Re: [Python-Dev] Semi-official read-only Github mirror of the CPython Mercurial repository

On Mon, Sep 30, 2013 at 7:08 AM, Skip Montanaro wrote: > > https://github.com/python/cpython is now live as a semi-official, *read > > only* Github mirror of the CPython Mercurial repository. Let me know if > you > > have any problems/concerns. > > Thanks for this, Eli. I use git regularly at wor

Re: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?

On 1 October 2013 00:35, Skip Montanaro wrote: > Splitting into two pieces also means you can implement it for 3.4 > first and identify possible problems caused by preexisting pip > installs before deciding whether to add it to 2.7 and 3.3. One of the key reasons for using the bootstrap mechanism

Re: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?

Splitting into two pieces also means you can implement it for 3.4 first and identify possible problems caused by preexisting pip installs before deciding whether to add it to 2.7 and 3.3. Skip ___ Python-Dev mailing list Python-Dev@python.org https://mai

Re: [Python-Dev] Semi-official read-only Github mirror of the CPython Mercurial repository

> https://github.com/python/cpython is now live as a semi-official, *read > only* Github mirror of the CPython Mercurial repository. Let me know if you > have any problems/concerns. Thanks for this, Eli. I use git regularly at work, so I'm getting much more comfortable with it. Do you have a sugge

Re: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?

On Sep 30, 2013, at 11:07 PM, Nick Coghlan wrote: >My plan now is to split the PEP in two, so the 3.4 changes can be accepted >as non-controversial, including the offer of core dev assistance in >creating and maintaining a Windows installer for pip to better support >earlier versions. The backport

Re: [Python-Dev] Semi-official read-only Github mirror of the CPython Mercurial repository

> > https://github.com/python/cpython is now live as a semi-official, *read > only* Github mirror of the CPython Mercurial repository. Let me know if you > have any problems/concerns. > > I still haven't decided how often to update it (considering either just N > times a day, or maybe use a Hg hook

Re: [Python-Dev] Semi-official read-only Github mirror of the CPython Mercurial repository

On Sep 30, 2013, at 9:09 AM, Eli Bendersky wrote: > Hi all, > > https://github.com/python/cpython is now live as a semi-official, *read only* > Github mirror of the CPython Mercurial repository. Let me know if you have > any problems/concerns. > > I still haven't decided how often to update

[Python-Dev] Semi-official read-only Github mirror of the CPython Mercurial repository

Hi all, https://github.com/python/cpython is now live as a semi-official, *read only* Github mirror of the CPython Mercurial repository. Let me know if you have any problems/concerns. I still haven't decided how often to update it (considering either just N times a day, or maybe use a Hg hook for

Re: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?

On 30 Sep 2013 21:52, Martin v. Löwis wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am 30.09.13 13:18, schrieb Donald Stufft: > > Well the point we tried to get across in the PEP is that a normal > > feature you can typically just install a backport from PyPI to gain > > it early.

Re: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 30.09.13 13:18, schrieb Donald Stufft: > Well the point we tried to get across in the PEP is that a normal > feature you can typically just install a backport from PyPI to gain > it early. This isin't so much driven by "well it'd be nice for the > s

Re: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?

On 30 Sep 2013 19:03, Martin v. Löwis wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Am 25.09.13 23:33, schrieb Donald Stufft: > > An early draft of this did not have the backport to 2.7 and when I > > showed *that* version around to get feedback people were less > > enthusiastic a

Re: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?

On Sep 30, 2013, at 5:01 AM, "Martin v. Löwis" wrote: > Signed PGP part > Am 25.09.13 23:33, schrieb Donald Stufft: > > An early draft of this did not have the backport to 2.7 and when I > > showed *that* version around to get feedback people were less > > enthusiastic about it and generally vie

Re: [Python-Dev] PEP 453 (pip bootstrapping) ready for pronouncement?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 25.09.13 23:33, schrieb Donald Stufft: > An early draft of this did not have the backport to 2.7 and when I > showed *that* version around to get feedback people were less > enthusiastic about it and generally viewed it as "nice but > worthless to m

Re: [Python-Dev] Getting Tulip (PEP 3156) into the 3.4 stdlib, marked provisional, named asyncio

On Mon, Sep 30, 2013 at 1:51 AM, Larry Hastings wrote: > My guess is, a lot of people would be disappointed if Tulip missed 3.4. I > suspect the community would rather we slip the beta a little if it meant it > the difference between Tulip and no Tulip. +1 ___