Re: [Python-Dev] Criticism of execfile() removal in Python3

2014-06-17 Thread Nick Coghlan
On 18 Jun 2014 01:59, "Chris Barker" wrote: > > By the way: iPython, while coming from, and heavily used by, the scientific/numeric computing community, is a great tool for all sorts of other python development as well. But probably too heavyweight for micropython. (we're drifting off topic, so t

Re: [Python-Dev] Issue 21671: CVE-2014-0224 OpenSSL upgrade to 1.0.1h on Windows required

2014-06-17 Thread M.-A. Lemburg
On 17.06.2014 22:36, Antoine Pitrou wrote: > Le 17/06/2014 14:55, M.-A. Lemburg a écrit : >> >> Alternatively, you could make use of our pyOpenSSL distribution, >> which includes pyOpenSSL and the OpenSSL libs (also for Windows): >> >> http://www.egenix.com/products/python/pyOpenSSL/ >> >> We creat

Re: [Python-Dev] Issue 21671: CVE-2014-0224 OpenSSL upgrade to 1.0.1h on Windows required

2014-06-17 Thread Antoine Pitrou
Le 17/06/2014 14:55, M.-A. Lemburg a écrit : Alternatively, you could make use of our pyOpenSSL distribution, which includes pyOpenSSL and the OpenSSL libs (also for Windows): http://www.egenix.com/products/python/pyOpenSSL/ We created this to address the problem of having to update OpenSSL ra

Re: [Python-Dev] Issue 21671: CVE-2014-0224 OpenSSL upgrade to 1.0.1h on Windows required

2014-06-17 Thread Benjamin Peterson
On Tue, Jun 17, 2014, at 12:03, Ned Deily wrote: > In article > <81f84430ce0242e5bfa5b2264777d...@blupr03mb389.namprd03.prod.outlook.com > >, > Steve Dower wrote: > > You'll only need to rebuild the _ssl and _hashlib extension modules with > > the > > new OpenSSL version. The easiest way to do

Re: [Python-Dev] Issue 21671: CVE-2014-0224 OpenSSL upgrade to 1.0.1h on Windows required

2014-06-17 Thread Ned Deily
In article <81f84430ce0242e5bfa5b2264777d...@blupr03mb389.namprd03.prod.outlook.com >, Steve Dower wrote: > You'll only need to rebuild the _ssl and _hashlib extension modules with the > new OpenSSL version. The easiest way to do this is to build from source > (which has already been updated f

Re: [Python-Dev] Issue 21671: CVE-2014-0224 OpenSSL upgrade to 1.0.1h on Windows required

2014-06-17 Thread M.-A. Lemburg
On 17.06.2014 20:27, Steve Dower wrote: > Yates, Andy (CS Houston, TX) wrote: >> Python Dev, >> Andy here. I have a Windows product based on Python and I'm getting hammered >> to >> release a version that includes the fix in OpenSSL 1.0.1h. My product is >> built >> on a Windows system using Pyth

Re: [Python-Dev] Issue 21671: CVE-2014-0224 OpenSSL upgrade to 1.0.1h on Windows required

2014-06-17 Thread Steve Dower
Yates, Andy (CS Houston, TX) wrote: > Python Dev, > Andy here. I have a Windows product based on Python and I'm getting hammered > to > release a version that includes the fix in OpenSSL 1.0.1h. My product is built > on a Windows system using Python installed from the standard Python installer >

[Python-Dev] Issue 21671: CVE-2014-0224 OpenSSL upgrade to 1.0.1h on Windows required

2014-06-17 Thread Yates, Andy (CS Houston, TX)
Python Dev, Andy here. I have a Windows product based on Python and I'm getting hammered to release a version that includes the fix in OpenSSL 1.0.1h. My product is built on a Windows system using Python installed from the standard Python installer at Python.org. I would be grateful if I could

Re: [Python-Dev] Criticism of execfile() removal in Python3

2014-06-17 Thread Chris Barker
On Mon, Jun 16, 2014 at 3:39 PM, Nick Coghlan wrote: > > FWIW, when I started using python (15?) years ago -- the first thing I > looked for was a way to "just run a file", at the interactive prompt, like > I had in MATLAB. I found and used execfile(). > > Yes, if people are looking for a MATLAB

Re: [Python-Dev] Windows XP, Python 3.5 and PEP 11

2014-06-17 Thread Mark Lawrence
On 17/06/2014 08:03, Victor Stinner wrote: 2014-06-17 7:01 GMT+02:00 Tim Golden : On 17/06/2014 04:08, Zachary Ware wrote: This was recently discussed in the "Moving Python 3.5 on Windows to a new compiler" thread, where Martin declared XP support to be ended [1]. I believe Tim Golden is the o

[Python-Dev] Commit "avoid a deadlock with the interpreter head lock and the GIL during finalization"

2014-06-17 Thread Victor Stinner
Hi, I just saw a change in Python finalization related to threads. I'm not sure that it is correct to not call tstate_delete_common(). Is this change related to an issue? I don't see any specific test. --- changeset 91234:5ccb6901cf95 3.4 avoid a deadlock with the interpreter head lock and the G

Re: [Python-Dev] Windows XP, Python 3.5 and PEP 11

2014-06-17 Thread Victor Stinner
2014-06-17 7:01 GMT+02:00 Tim Golden : > On 17/06/2014 04:08, Zachary Ware wrote: >> This was recently discussed in the "Moving Python 3.5 on Windows to a >> new compiler" thread, where Martin declared XP support to be ended >> [1]. I believe Tim Golden is the only resident Windows dev from whom >