Re: [Python-Dev] pip: cdecimal an externally hosted file and may be unreliable [sic]

2014-05-06 Thread Victor Stinner
Hi, I don't understand your email. Can you please elaborate? Victor 2014-05-06 23:35 GMT+02:00 Stefan Krah : > Just a warning, in case any of the new packaging team forgot to contact > http://cve.mitre.org/ . > > > Stefan Krah > > > > ___ > Python-Dev

[Python-Dev] pip: cdecimal an externally hosted file and may be unreliable [sic]

2014-05-06 Thread Stefan Krah
Just a warning, in case any of the new packaging team forgot to contact http://cve.mitre.org/ . Stefan Krah ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/ma

Re: [Python-Dev] Python under the sea and in space

2014-05-06 Thread Terry Reedy
On 5/4/2014 11:02 PM, Jessica McKellar wrote: Hi folks, I'm trying to determine the greatest depth (in the ocean or underground) and highest altitude at which Python code has been executed. Please note that I'm interested in where the code was executed, and not, say, where data that Python anal

Re: [Python-Dev] Existence of pythonNN.zip in sys.path

2014-05-06 Thread Terry Reedy
On 5/5/2014 5:32 PM, Anthony Tuininga wrote: Hi, I am the author of cx_Freeze which creates "frozen" executables from Python scripts. To this point I have been using frozen modules (compiled C) but this has the side effect of bundling parts of Python with a cx_Freeze release -- and this has bitt

Re: [Python-Dev] Behaviour change of object().format()

2014-05-06 Thread Eric V. Smith
On 05/06/2014 10:33 AM, James Swift wrote: > Hi, > > In 3.3 I could do the following > "{x:s}".format(**{'x': [1, 2, 3]}) > '[1, 2, 3]' > > But in 3.4 > "{x:s}".format(**{'x': [1, 2, 3]}) > Traceback (most recent call last): > File "", line 1, in > TypeError: non-empty format strin

Re: [Python-Dev] Behaviour change of object().format() in 3.4

2014-05-06 Thread R. David Murray
On Tue, 06 May 2014 16:45:52 +0200, James Swift wrote: > Hi, > > In 3.3 I could do the following > > >>> "{x:s}".format(**{'x': [1, 2, 3]}) > '[1, 2, 3]' > > But in 3.4 > > >>> "{x:s}".format(**{'x': [1, 2, 3]}) > Traceback (most recent call last): > File "", line 1, in > TypeError: non-emp

[Python-Dev] Behaviour change of object().format() in 3.4

2014-05-06 Thread James Swift
Hi, In 3.3 I could do the following >>> "{x:s}".format(**{'x': [1, 2, 3]}) '[1, 2, 3]' But in 3.4 >>> "{x:s}".format(**{'x': [1, 2, 3]}) Traceback (most recent call last): File "", line 1, in TypeError: non-empty format string passed to object.__format__ Is this intentional? regards, Jame

[Python-Dev] Behaviour change of object().format()

2014-05-06 Thread James Swift
Hi, In 3.3 I could do the following >>> "{x:s}".format(**{'x': [1, 2, 3]}) '[1, 2, 3]' But in 3.4 >>> "{x:s}".format(**{'x': [1, 2, 3]}) Traceback (most recent call last): File "", line 1, in TypeError: non-empty format string passed to object.__format__ Is this intentional? regards, Jame