Terry Reedy wrote:
> "Ant" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
>>Looks like some good new stuff coming along. Does anyone know what's
>>happened to the path PEP (http://www.python.org/doc/peps/pep-0355/) - I
>>thought I'd seen somewhere that that was originally planned
"Ant" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Looks like some good new stuff coming along. Does anyone know what's
> happened to the path PEP (http://www.python.org/doc/peps/pep-0355/) - I
> thought I'd seen somewhere that that was originally planned for 2.5...
It is still
Looks like some good new stuff coming along. Does anyone know what's
happened to the path PEP (http://www.python.org/doc/peps/pep-0355/) - I
thought I'd seen somewhere that that was originally planned for 2.5...
--
Ant...
--
http://mail.python.org/mailman/listinfo/python-list
"Tim Peters" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>> For more details about the plan for Python 2.5, see:
>>
>> http://www.python.org/doc/peps/pep-0356/
>
> Looks like links to PEPs are completely hosed at the moment. For
> example, the link above displays an empty dir
> For more details about the plan for Python 2.5, see:
>
> http://www.python.org/doc/peps/pep-0356/
Looks like links to PEPs are completely hosed at the moment. For
example, the link above displays an empty directory, and
http://www.python.org/doc/peps
displays a directory full of empty
Only MS can answer those questions.
Even though, Python on Windows is compiled with VC++, you can still use
Mingw32 to compile extensions. There are some articles floating around
on how to do this and I did try it successfully in the past. Please
note that I am not advocating either compiler. Just
Ravi Teja wrote:
> http://msdn.microsoft.com/visualc/vctoolkit2003/
> Free.
>
True, but 'The Microsoft Toolkit Compiler doesn't come out-of-the-box
with everything you need to compile extensions.' see:
http://www.vrplumber.com/programming/mstoolkit/
If you are going ahead with the VC 7.1 Toolk
Ben Finney wrote:
>> - ASCII is the default coding
>
> Er? How did this happen?
>
> To be specific, what about all the movement toward UTF-8?
See PEP 263. ASCII is the default encoding for source code;
if you want to use UTF-8 in source code, either put
# -*- coding: utf-8 -*-
into the fil
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes:
> For more details about the plan for Python 2.5, see:
> http://www.python.org/doc/peps/pep-0356/
Thanks for bringing attention to this.
> - ASCII is the default coding
Er? How did this happen?
To be specific, what about all the movement
http://msdn.microsoft.com/visualc/vctoolkit2003/
Free.
--
http://mail.python.org/mailman/listinfo/python-list
Scott David Daniels wrote:
> I think there will be no compiler switching for a while. The previous
> switch from VC 6 was in part because there was no longer any legal way
> to get a VC 6.0 compiler. This round at least is sticking with the same
> compiler as Python 2.4 (VC 7.0).
>
Scott:
Adm
Pekka Niiranen wrote:
> what I would like to see in (www.python.org) is
> Windows installation package (*.msi)
> compiled with option "--enable-unicode=ucs4".
> See http://www.xml.com/pub/a/2005/06/15/py-xml.html
Just enabling that option is not enough: the resulting
binary likely crashes. In addi
Gregory Petrosyan wrote:
> P.P.S. are there any experiments with compiling CPython with Intel's
> compiler?
Yup, the (older) Intel compiler was quite effective for 2,2 and 2.3
(at least), and I think at least one distro was built with it.
--
-Scott David Daniels
[EMAIL PROTECTED]
--
http://mail.
Hi,
what I would like to see in (www.python.org) is
Windows installation package (*.msi)
compiled with option "--enable-unicode=ucs4".
See http://www.xml.com/pub/a/2005/06/15/py-xml.html
-pekka-
--
http://mail.python.org/mailman/listinfo/python-list
Yes, it's very annoying to see VC8 warnings on perfectly legal C
constructs (AFAIK even sprinf is now considered "unsafe", MS wants
everybody to use sprintf_s). But the optimisation capacities of VC8 are
really great. Maybe someone can measure the speedup?
P.S. there's an "_CRT_SECURE_NO_DEPRECATE
Don Taylor wrote:
> [EMAIL PROTECTED] wrote:
>> For more details about the plan for Python 2.5, see:
>> http://www.python.org/doc/peps/pep-0356/
> I hope that this is not considered too off topic, but what compiler is
> going to be used for the MSW version of 2.5?
>
> If it is going to the MS
[EMAIL PROTECTED] wrote:
> For more details about the plan for Python 2.5, see:
>
> http://www.python.org/doc/peps/pep-0356/
>
I hope that this is not considered too off topic, but what compiler is
going to be used for the MSW version of 2.5?
If it is going to the MS Visual Studio 2005 com
For more details about the plan for Python 2.5, see:
http://www.python.org/doc/peps/pep-0356/
The highlights are that we are hoping to put out the first alpha Real
Soon Now, hopefully in a week or two. If there's something you really
think just must be in 2.5 and can't wait until 2.6, now is
18 matches
Mail list logo
