Re: [Python-Dev] The socket HOWTO

2011-05-29 Thread Gregory P. Smith
On Sun, May 22, 2011 at 11:22 PM, Nick Coghlan ncogh...@gmail.com wrote: On Sun, May 22, 2011 at 3:38 AM, Georg Brandl g.bra...@gmx.net wrote: On 05/21/11 18:01, Senthil Kumaran wrote: So a rewrite with good pointers would be more appropriate. Even then, it's better off in the Wiki until

Re: [Python-Dev] [Python-checkins] cpython (3.2): Fix ProcessTestCasePOSIXPurePython to test the module from import when

2011-05-29 Thread Nick Coghlan
On Sun, May 29, 2011 at 2:13 AM, gregory.p.smith python-check...@python.org wrote: Ironically: I don't think any platform should ever actually _use_ the pure Python subprocess code on POSIX platforms anymore.  This at least tests it properly in this stable branch.  The pure python code for

Re: [Python-Dev] [Python-checkins] cpython (3.2): Fix ProcessTestCasePOSIXPurePython to test the module from import when

2011-05-29 Thread Nick Coghlan
On Sun, May 29, 2011 at 11:08 PM, Nick Coghlan ncogh...@gmail.com wrote: On Sun, May 29, 2011 at 2:13 AM, gregory.p.smith python-check...@python.org wrote: Ironically: I don't think any platform should ever actually _use_ the pure Python subprocess code on POSIX platforms anymore.  This at

Re: [Python-Dev] The socket HOWTO

2011-05-29 Thread Martin v. Löwis
I would like to suggest that we remove the socket HOWTO (currently at http://docs.python.org/dev/howto/sockets.html) -1. I think there should be a Python-oriented introduction to sockets. You may have complaints about the specific wording of the text, but please understand that these are

[Python-Dev] PhD ideas

2011-05-29 Thread Tiago Boldt Sousa
Hi, I'm now currently finishing my MsC and am thinking about enrolling into the PhD program. I was wondering if any of you would like to suggest me some research topic that could benefit the scientific community, that might also result as a potential improvement for Python. I love everything

[Python-Dev] [RELEASE] 3.1.4 release candidate 1

2011-05-29 Thread Benjamin Peterson
On behalf of the Python development team, I'm happy as a swallow to announce a release candidate for the fourth bugfix release for the Python 3.1 series, Python 3.1.4. 3.1.4 will the last bug fix release in the 3.1 series before 3.1. After 3.1.4, 3.1 will be in security-only fix mode. The Python

[Python-Dev] [RELEASE] Python 2.7.2 release candidate 1

2011-05-29 Thread Benjamin Peterson
On behalf of the Python development team, I'm happy to announce the immediate availability of Python 2.7.2 release candidate 1. 2.7.2 is the second in bugfix release for the Python 2.7 series. 2.7 is the last major verison of the 2.x line and will be receiving bug fixes while new feature

Re: [Python-Dev] [RELEASE] Python 2.7.2 release candidate 1

2011-05-29 Thread Jack Diederich
On Sun, May 29, 2011 at 6:47 PM, Benjamin Peterson benja...@python.org wrote: 2.7.2 is the second in bugfix release for the Python 2.7 series. 2.7 is the last major verison of the 2.x line and will be receiving bug fixes while new feature development focuses on 3.x. 2.7 includes many

Re: [Python-Dev] [RELEASE] Python 2.7.2 release candidate 1

2011-05-29 Thread Benjamin Peterson
2011/5/29 Jack Diederich jackd...@gmail.com: On Sun, May 29, 2011 at 6:47 PM, Benjamin Peterson benja...@python.org wrote: 2.7.2 is the second in bugfix release for the Python 2.7 series. 2.7 is the last major verison of the 2.x line and will be receiving bug fixes while new feature

Re: [Python-Dev] [RELEASE] Python 2.7.2 release candidate 1

2011-05-29 Thread Carl Meyer
On 05/29/2011 06:11 PM, Jack Diederich wrote: We don't, but many projects do release new features with bugfix version numbers - I'm looking at you, Django. Really? Do you have an example of a new Django feature that was released in a bugfix version number? Just curious, since that's

Re: [Python-Dev] [RELEASE] Python 2.7.2 release candidate 1

2011-05-29 Thread Ralf Schmitt
Benjamin Peterson benja...@python.org writes: The 2.7.2 changelog is at: http://hg.python.org/cpython/file/439396b06416/Misc/NEWS The news file mentions that issue 1195 (Problems on Linux with Ctrl-D and Ctrl-C during raw_input) is fixed. That's not true, see: