Dan Eloff schrieb:
I just want to say thank you, very much, from the bottom of my heart,
to everyone here who chooses to spend some of their free time working
on improving Python.
Hi Dan,
I can't really speak for all the other contributors (but maybe in
this case I can): Thanks for the kind
Hi all,
There are more cases of signed integer overflows in the CPython source
code base...
That's on a 64-bits machine:
[GCC 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)] on linux2
abs(-sys.maxint-1) == -sys.maxint-1
I'd expect the same breakage everywhere when GCC 4.2 is used. Note
I've been porting the grammar for pydev to version 2.5 and I've seen
that you can now declare a class in the format: class B():pass
(without the testlist)
-- from the grammar: classdef: 'class' NAME ['(' [testlist] ')'] ':' suite
I think that this change should be presented at
I think that this change should be presented at
http://docs.python.org/dev/whatsnew/whatsnew25.html
It's already listed there: http://docs.python.org/dev/whatsnew/other-lang.html
--
Lawrence
http://www.oluyede.org/blog
___
Python-Dev mailing list
The test suite currently (2.5) has two failures on Windows
if Python is installed into a directory with a space in it
(such as Program Files). The failing tests are test_popen
and test_cmd_line.
The test_cmd_line failure is shallow: the test fails to properly
quote sys.executable when passing it
Fabio Zadrozny wrote:
I've been porting the grammar for pydev to version 2.5 and I've seen
that you can now declare a class in the format: class B():pass
(without the testlist)
-- from the grammar: classdef: 'class' NAME ['(' [testlist] ')'] ':' suite
I think that this change should be
On Sat, 16 Sep 2006 19:22:34 +0200, \Martin v. Löwis\ [EMAIL PROTECTED]
wrote:
The test suite currently (2.5) has two failures on Windows
if Python is installed into a directory with a space in it
(such as Program Files). The failing tests are test_popen
and test_cmd_line.
The test_cmd_line
On 9/13/06, Sanghyeon Seo [EMAIL PROTECTED] wrote:
CPython 2.5, which will be released Real Soon Now, is the firstversion to ship with new AST branch, which have been in developmentfor a long time.AST branch uses ASDL, Abstract Syntax Description Language
http://asdl.sourceforge.net/ to describe
Martin v. Löwis wrote:
The test suite currently (2.5) has two failures on Windows
if Python is installed into a directory with a space in it
(such as Program Files). The failing tests are test_popen
and test_cmd_line.
The test_cmd_line failure is shallow: the test fails to properly
quote
[Martin v. Löwis]
...
Can somebody remember what the reason is to invoke cmd.exe (or COMSPEC)
in os.popen?
Absolutely necessary, as any number of shell gimmicks can be used in
the passed string, same as on non-Windows boxes; .e.g.,
import os
os.environ['STR'] = 'SSL'
p = os.popen(findstr
Nick Coghlan wrote:
As for the reason: it makes it possible to use the same style for classes
without bases as is used for functions without arguments. Prior to this
change, there was a sharp break in the class syntax, such that if you got rid
of the last base class you had to get rid of
On 9/16/06, Talin [EMAIL PROTECTED] wrote:
Nick Coghlan wrote:
As for the reason: it makes it possible to use the same style for classes
without bases as is used for functions without arguments. Prior to this
change, there was a sharp break in the class syntax, such that if you got
rid
On 9/16/06, Lawrence Oluyede [EMAIL PROTECTED] wrote:
I think that this change should be presented at
http://docs.python.org/dev/whatsnew/whatsnew25.html
It's already listed there: http://docs.python.org/dev/whatsnew/other-lang.html
Thanks... also, I don't know if the empty yield statement
That was my first thought as well. Unfortunately a quick test shows
that class Foo(): creates an old style class instead :(
I think that's because until it'll be safe to break things we will
stick with classic by default...
--
Lawrence
http://www.oluyede.org/blog
Lawrence Oluyede wrote:
That was my first thought as well. Unfortunately a quick test shows
that class Foo(): creates an old style class instead :(
I think that's because until it'll be safe to break things we will
stick with classic by default...
But in this case nothing will be broken,
Talin wrote:
Is the result a new-style or classic-style class? It would be nice if
using the empty parens forced a new-style class...
No, it wouldn't, IMO. Too subtle a clue.
Best to just wait for Py3k when all classes will
be new-style.
--
Greg
On 9/16/06, Talin [EMAIL PROTECTED] wrote:
Lawrence Oluyede wrote: That was my first thought as well.Unfortunately a quick test shows that class Foo(): creates an old style class instead :( I think that's because until it'll be safe to break things we will
stick with classic by default...But in
17 matches
Mail list logo
