Hi Georg!
On Sat, Aug 30, 2008 at 11:09 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
> Ondrej Certik schrieb:
Ondrej
>>>
>>> Ondrej, a patch that improves the official docs would be welcome and still
>>> potentially make 2.6/3.0
>>
>> That'd be awesome. I need to finish my thesis in the next c
Le Sat, 30 Aug 2008 23:15:13 +0200, Tarek Ziadé a écrit :
> On Sat, Aug 30, 2008 at 10:30 PM, KLEIN Stéphane
> <[EMAIL PROTECTED]>wrote:
>
>> Hello,
>>
>> I wonder if optparse is dead ? because :
>>
>> * svn access is down (svn co svn://starship.python.net/optik/trunk
>> optik) ( http://sourcefor
On Sat, Aug 30, 2008 at 10:30 PM, KLEIN Stéphane <[EMAIL PROTECTED]>wrote:
> Hello,
>
> I wonder if optparse is dead ? because :
>
> * svn access is down (svn co svn://starship.python.net/optik/trunk optik)
> ( http://sourceforge.net/mailarchive/forum.php?
> thread_name=466F541C.6010804%40users.so
KLEIN Stéphane schrieb:
> Hello,
>
> I wonder if optparse is dead ? because :
>
> * svn access is down (svn co svn://starship.python.net/optik/trunk optik)
> ( http://sourceforge.net/mailarchive/forum.php?
> thread_name=466F541C.6010804%40users.sourceforge.net&forum_name=optik-
> users )
>
> * l
Ondrej Certik schrieb:
>>> Ondrej
>>
>> Ondrej, a patch that improves the official docs would be welcome and still
>> potentially make 2.6/3.0
>
> That'd be awesome. I need to finish my thesis in the next couple days,
> so I'd welcome if anyone could just take it and put usefult things in.
> I cou
Hello,
I wonder if optparse is dead ? because :
* svn access is down (svn co svn://starship.python.net/optik/trunk optik)
( http://sourceforge.net/mailarchive/forum.php?
thread_name=466F541C.6010804%40users.sourceforge.net&forum_name=optik-
users )
* last release is out 2 years ago
( http://sour
On Sat, Aug 30, 2008 at 1:06 PM, Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I was working on a recursion overflow checking bug
> (http://bugs.python.org/issue2548) and, while I've managed to produce a
> working
> patch, I've also become uncomfortable with the very idea of trying to plug
Hi,
I was working on a recursion overflow checking bug
(http://bugs.python.org/issue2548) and, while I've managed to produce a working
patch, I've also become uncomfortable with the very idea of trying to plug all
those holes just for the sake of plugging them. I'll try to explain why, by
describ
>> Ondrej
>
> Ondrej, a patch that improves the official docs would be welcome and still
> potentially make 2.6/3.0
That'd be awesome. I need to finish my thesis in the next couple days,
so I'd welcome if anyone could just take it and put usefult things in.
I could get to do it the next week the e
On Aug 30, 2008, at 2:41 PM, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
I strongly advise people interested in this topic to take a closer
look
at the functionality that was added to address issue 2235. The "don't
inherit __hash__" behaviour has been backported from 3.0 and broke a
bunch of
> I strongly advise people interested in this topic to take a closer look
> at the functionality that was added to address issue 2235. The "don't
> inherit __hash__" behaviour has been backported from 3.0 and broke a
> bunch of code, but the naive fix of reverting to the 2.5 behaviour
> proceeded t
Michal Revucky schrieb:
> hello everyone,
>
> i would like to get a python script which executes all interpreter's opcodes,
> or
> how am i supposed to create such script... i just need to make sure that all
> opcodes (as defined in Include/opcode.h) are executed by this scrip
> i need this scri
hello everyone,
i would like to get a python script which executes all interpreter's opcodes, or
how am i supposed to create such script... i just need to make sure that all
opcodes (as defined in Include/opcode.h) are executed by this scrip
i need this script for testing purposes while rewrittin
13 matches
Mail list logo
