Brett Cannon wrote:
> On Jan 10, 2008 8:39 AM, Joe Angell <[EMAIL PROTECTED]> wrote:
>
>> My apologies if this has been asked before, but are there any plans to
>> add the compiler module back in to py3k? If so, any idea on a
>> timeline? If help is needed I may be able to put in some time on
Raymond Hettinger schrieb:
> I proposed to remove three methods from the queue module, qsize(),
> empty(), and full(). These are not reliable. The RightWay (tm) is
> to trap the Empty and Full exceptions or use the .join() approach.
I am actively using empty(). This code example receives and pr
On Jan 11, 2008 11:16 AM, Aahz <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 11, 2008, Raymond Hettinger wrote:
> >
> > I proposed to remove three methods from the queue module, qsize(),
> > empty(), and full(). These are not reliable. The RightWay (tm) is to
> > trap the Empty and Full exceptions or
On 11-Jan-08, at 11:13 AM, Raymond Hettinger wrote:
> I proposed to remove three methods from the queue module, qsize(),
> empty(), and full(). These are not reliable. The RightWay (tm) is
> to trap the Empty and Full exceptions or use the .join() approach.
-1. There are several "advisory"
On Fri, Jan 11, 2008, Raymond Hettinger wrote:
>
> I proposed to remove three methods from the queue module, qsize(),
> empty(), and full(). These are not reliable. The RightWay (tm) is to
> trap the Empty and Full exceptions or use the .join() approach.
Although I'm not going to advocate for re
I proposed to remove three methods from the queue module, qsize(), empty(), and
full(). These are not reliable. The RightWay (tm) is to trap the Empty and
Full exceptions or use the .join() approach.
Raymond
--- From the docs ---
Queue.qsize()¶
Return the approximate size of the queue.
Martin v. Löwis schrieb:
>> * you can parse things with parser.suite(), but not create an AST from
>>the parse result
>> * you can create an AST with an undocumented flag to compile(), but not
>>compile the resulting AST
>
> The flag is documented, in the document referred to.
>
> There a
On Fri, 11 Jan 2008 16:02:53 +0100, Georg Brandl <[EMAIL PROTECTED]> wrote:
>
>Python's code parsing/compiling interface is currently very cluttered:
>* you can parse things with parser.suite(), but not create an AST from
> the parse result
>* you can create an AST with an undocumented flag to co
On Jan 11, 2008, at 10:02 AM, Georg Brandl wrote:
> I'd suggest a single package to unify all this functionality and an
> API
> that makes it easy to go from every compiling stage to the next, or to
> the final code object.
+1
-Fred
--
Fred Drake
__
> * you can parse things with parser.suite(), but not create an AST from
>the parse result
> * you can create an AST with an undocumented flag to compile(), but not
>compile the resulting AST
The flag is documented, in the document referred to.
There are good reasons for why things are th
Brett Cannon schrieb:
> On Jan 10, 2008 2:08 PM, Joe Angell <[EMAIL PROTECTED]> wrote:
>> Oh I see... forgive my ignorance but could you point me at some
>> documentation or a project that uses the c AST as you mentioned? Is
>> that done through some part of the C-API? I cannot find that in the
>
11 matches
Mail list logo
