On Jun 2, 2008, at 11:59 PM, Guido van Rossum wrote:
Actually I think we won't need that function once we're used to just
passing exception instances around.
Ah, so many differences that I've lost track of. I feel so...
py2k. :-(
-Fred
--
Fred Drake
___
On Mon, Jun 2, 2008 at 8:56 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 2, 2008 at 9:46 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
>> On Mon, Jun 2, 2008 at 8:16 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
>>> On Mon, Jun 2, 2008 at 8:56 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
On Mon, Jun 2, 2008 at 9:46 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 2, 2008 at 8:16 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
>> On Mon, Jun 2, 2008 at 8:56 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
>>> On May 31, 2008, at 6:42 PM, Tim Delaney wrote:
This reminds me
On Mon, Jun 2, 2008 at 5:00 PM, Giovanni Bajo <[EMAIL PROTECTED]> wrote:
> Python 3.0 defaults to "-tt" (error on inconsistent usage of tab and
> spaces). Then: why is there still a "-t" and "-tt" command line option?
> Is just a relic that should be removed?
Probably. Though there are plenty of p
On Mon, Jun 2, 2008 at 8:16 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 2, 2008 at 8:56 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
>> On May 31, 2008, at 6:42 PM, Tim Delaney wrote:
>>>
>>> This reminds me of something I've thought a few times - maybe the tuple
>>> returned from sys.exc_
Collin Winter gmail.com> writes:
>
> See PEP 3109: http://www.python.org/dev/peps/pep-3109/
By the way, this document mentions a "raise ... from ..." form, but it doesn't
seem to me it has been implemented. Perhaps the document should be corrected?
Also, it doesn't mention the with_traceback()
Travis Oliphant ieee.org> writes:
> This should be clarified in the PEP. Can you take a stab at it?
Here's a patch for what I think the locking protocol part should look like. It
changes the "passing NULL as Py_buffer" bit into a requirement to always pass a
Py_buffer structure, and distinguishe
Travis Oliphant wrote:
> This should be clarified in the PEP. Can you take a stab at it?
Would this work?
Stefan
Index: pep-3118.txt
===
--- pep-3118.txt (Revision 63861)
+++ pep-3118.txt (Arbeitskopie)
@@ -153,10 +153,8 @@
This
Hello,
Python 3.0 defaults to "-tt" (error on inconsistent usage of tab and
spaces). Then: why is there still a "-t" and "-tt" command line option?
Is just a relic that should be removed?
Thanks!
--
Giovanni Bajo
Develer S.r.l.
http://www.develer.com
__
On Mon, Jun 2, 2008 at 8:56 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
> On May 31, 2008, at 6:42 PM, Tim Delaney wrote:
>>
>> This reminds me of something I've thought a few times - maybe the tuple
>> returned from sys.exc_info() should be a named tuple.
>
> +1
It should be replaced with a functio
On May 31, 2008, at 6:42 PM, Tim Delaney wrote:
This reminds me of something I've thought a few times - maybe the
tuple returned from sys.exc_info() should be a named tuple.
+1
-Fred
--
Fred Drake
___
Python-3000 mailing list
Python-3000@
On Mon, Jun 2, 2008 at 7:22 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
>>
>
> Now is as good a time as any to mention that on Wednesday I am flying
> out to help my mother move. I don't know when she is going to have her
> Internet connection set up, so I might not be back online until June
> 16.
On Mon, Jun 2, 2008 at 3:51 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> We are going to postpone the first beta releases by one week. We had some
> problems with mail.python.org today, which prompted a query to Guido from me
> about the postpon
On Tue, Jun 3, 2008 at 7:30 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> On Sun, Jun 1, 2008 at 6:21 PM, Greg Ewing <[EMAIL PROTECTED]> wrote:
>> Atsuo Ishimoto wrote:
>>
>>> I'm not comfortable with "printable", too. Is "legible" better? This
>>> is first time for me to see this word in my li
On Mon, Jun 2, 2008 at 4:09 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I will freely admit that I haven't followed this thread in any detail,
> but if it were up to me, I'd have the 2.6 internal code use PyString
...
Should we read this as a BDFL pronouncement and make it so?
All that wo
I will freely admit that I haven't followed this thread in any detail,
but if it were up to me, I'd have the 2.6 internal code use PyString
(as both what the linker sees and what the human reads in the source
code) and the 3.0 code use PyBytes for the same thing. Let the merges
be damed -- most cha
On 6/2/08, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> I believe those APIs are already there in the existing interface. Why does
> that concern you?
Just because PyBytes_InternXXX are not in Py3K C API. Iff the whole
point of this patch is easier merges, then I believe there is a
problem here.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We are going to postpone the first beta releases by one week. We had
some problems with mail.python.org today, which prompted a query to
Guido from me about the postponement. mail.python.org should now be
back up normally now, as evidenced by
Atsuo Ishimoto writes:
> Okay, we'll keep 'strict' as default error handler for stdout always,
> then. I can live with it.
> But, my $0.02, I expect this issue will be revisited after people
> start to develop real applications with Python 3.x.
I agree, I expect it to be revisited too. But i
On Sun, Jun 1, 2008 at 6:21 PM, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Atsuo Ishimoto wrote:
>
>> I'm not comfortable with "printable", too. Is "legible" better? This
>> is first time for me to see this word in my life :).
>
> The term "printable" has a long history in computing of
> meaning that
On Mon, Jun 2, 2008 at 5:33 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
>
>> Okay, how about this? http://codereview.appspot.com/1521
>>
>> Using that patch, both PyString_ and PyBytes_ APIs are available using
>> function stubs similar to the above. I opted to define the stub
>> functions righ
On 2008-06-02 01:30, Gregory P. Smith wrote:
On Fri, May 30, 2008 at 1:37 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
Sorry, I probably wasn't clear enough:
Why can't we have both PyString *and* PyBytes exposed as C
APIs (ie. visible in code and in the linker) in 2.x, with one redirecting
to t
Are you completelly sure of adding those guys: PyBytes_InternXXX ???
On 6/1/08, Gregory P. Smith <[EMAIL PROTECTED]> wrote:
> On Fri, May 30, 2008 at 1:37 AM, M.-A. Lemburg <[EMAIL PROTECTED]> wrote:
> > On 2008-05-30 00:57, Nick Coghlan wrote:
> >>
> >> M.-A. Lemburg wrote:
> >>>
> >>> * W
23 matches
Mail list logo
