Nick Coghlan [EMAIL PROTECTED] wrote:
Rather than trying to change course midstream, I *like* the fact that
the PEP 352 hierarchy introduces BaseException to bring the language
itself into line with what people have already been taught. Breaking
things in Py3k is all well and good, but
Testing submission from dinsdale.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Sigh. Enough already. PEP 352 was chosen to minimize incompatibilities
and maximize gain with minimal changes in the tree. Also note that
Warnings can sometimes be raised and should then treated as errors, so
Warning would have to inherit from Error.
I vote for the status quo in HEAD, except I've
Giovanni Bajo wrote:
OTOH, I also understand that people have been told that deriving from
Exception
is the right thing to do forever now.
Have we really being telling them to derive *directly*
from Exception, or just that deriving somehow from
Exception will become mandatory?
For the
On 3/19/06, Greg Ewing [EMAIL PROTECTED] wrote:
Have we really being telling them to derive *directly*
from Exception, or just that deriving somehow from
Exception will become mandatory?
It doesn't matter. Most code that tries to be a good citizen today
derives its exceptions from Exception.
On 3/18/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The comma and as have different precedence in your proposed except clause
than they currently do in the import statement. I think that can lead to
confusion. In particular, if someone is used to
from foo import bar, baz as flurp
I
On 3/18/06, Barry Warsaw [EMAIL PROTECTED] wrote:
On Fri, 2006-03-17 at 23:48 -0800, Neal Norwitz wrote:
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C)
On Sun, 2006-03-19 at 19:45 -0800, Guido van Rossum wrote:
-1. See my response in the other thread. The focus on 'Error' is
mistaken, and we have a large body of existing code that derives from
Exception.
Just to be clear, are you saying -1 only for Python 2.5 or -1 also for
Python 3.0? If
On Mar 19, 2006, at 7:42 PM, Guido van Rossum wrote:
...
There seem to be other places where Python is beginning to require
parens
even though they aren't strictly necessary to resolve syntactic
ambiguity.
In the style guide only, I hope. The parens that are mandatory in a
few
I see increased activity related to Python 3000. This is great, but
there is some danger involved. Some of the dangers are: overloading
developers; setting unrealistic expectations for what can be
accomplished; scaring the more conservative user community; paralyzing
developers who can't decide
On 3/15/06, Georg Brandl [EMAIL PROTECTED] wrote:
Neil Schemenauer wrote:
I think it would be a good idea to follow the Plone project and try
to encourage new developers by offering assistance to get them up
and running. AFAIK, we've done that for the other bug days but it
might help to
On Saturday 18 March 2006 18:48, Neal Norwitz wrote:
Just in case anybody here's been snoozing, 2.5 alpha 1 is coming up
real quick, hopefully within a couple of weeks. If you have any
*major* features (particularly implemented in C) that you want to
see in 2.5, bring it up now. I want to
On Friday 2006-03-17 05:04, Alex Martelli wrote:
Hmmm, if we allowed '(expr as var)' for generic expr's we'd make
a lot of people pining for 'assignment as an expression' very happy,
wouldn't we...?
I hope not. It looks a lot more like a binding construct
than an assigning one. But what
Guido van Rossum wrote:
...
Please don't respond with answers to these questions -- each of them
is worth several threads. Instead, ponder them, and respond with a +1
or -1 on the creation of the python-3000 mailing list. We'll start
discussing the issues there -- or here, if the general
On Monday 20 March 2006 00:49, Anthony Baxter wrote:
I'd still like to push 2.4.3rc1 out in a couple of days time, with
2.4.3 final next week, and then maybe aim for 2.5a1 a week or two
later? How does that work for everyone?
I should be fine to build the documentation Wednesday night (US
15 matches
Mail list logo
