> Does it bother you that you need ()s to make instances elsewhere?
> That you have to type int('123') instead of int, '123'?
Not at all...Python never supported this.
Cheers,
David
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.or
> I can help. I don't have a patch against the trunk but my first
> revisions of the patch
> for annotations did handle things like tuple parameters which are
> relevant to 2.6.
Ah yes, I forgot about nested parameters. I see that 53170 still has
nested parameters, but they were removed at some la
At any rate, I am still interested if anyone has a working patch for
this against the trunk, or any pointers for adapting 53170, words of
experience when changing the grammar, additions to PEP 306, etc... any
help would be greatly appreciated!
David,
I can help. I don't have a patch against the
David Pokorny wrote:
[warning - mini rant]
Reason is, I am using 3.0a for now for this project, but I am sorry to
say that using parentheses for raising exceptions drives me up the
wall,
[warning - a bit of a counter-rant ;-]
Does it bother you that you need ()s to make instances elsewhere?
On Jun 19, 4:16 pm, "Guido van Rossum" <[EMAIL PROTECTED]> wrote:
> complex change to the syntax and code generator. Your motivation is
> also suspect: 2.6 is supposed to be a stepping stone towards 3.0, not
> a safe haven for people who don't like certain 3.0 features. Just get
Guilty as charged
On Thu, Jun 19, 2008 at 3:59 PM, David Pokorny <[EMAIL PROTECTED]> wrote:
> I am curious if there is any news on this issue. My understanding is
> that since this is a new feature, nothing will be committed until
> after 2.6 comes out, but it would be *really nice* if I could use
> annotations in 2
Hi,
I am curious if there is any news on this issue. My understanding is
that since this is a new feature, nothing will be committed until
after 2.6 comes out, but it would be *really nice* if I could use
annotations in 2.x.
[warning - mini rant]
Reason is, I am using 3.0a for now for this projec
