Ahh, ok, now I think I see...  there is clearly some other mechanism that
this warning is going through that we're not handling correctly.

I'll try and track it down.  Thanks!

-----Original Message-----
From: Matthew Wilkes [mailto:matt...@matthewwilkes.co.uk]
Sent: Monday, June 01, 2009 10:49 AM
To: Michael Foord
Cc: Dino Viehland; Python-Dev
Subject: Re: [Python-Dev] syntax warnings don't go through warnings.warn?


On 1 Jun 2009, at 18:42, Michael Foord wrote:

> Dino is developing Python - he's one of the core developers of
> IronPython

Ah, sorry, I'm bad with names, don't always pick up on who is who!

> and I suspect he is asking whether this is intentional, and
> IronPython should implement the same behaviour, or whether it is a
> bug.

The docs do seem to be clear though, warnings.warn creates a warning,
but there are multiple other ways to do it, it's a convenience method.

Matt

_______________________________________________
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

Reply via email to