Copied from c.l.p post by F. Lundh
I have no idea if this has implications for warnings in 2.6
------------------------

>  >>> from sympy.mpmath import specfun
>  >>>
>
> So what could be suppressing the warning?
[about 'as' becoming a keyword, when assigned to]

a bug in Python 2.5, it seems:

> more f1.py
as = 1
as = 2
as = 3
> python f1.py
f1.py:1: Warning: 'as' will become a reserved keyword in Python 2.6
f1.py:2: Warning: 'as' will become a reserved keyword in Python 2.6
f1.py:3: Warning: 'as' will become a reserved keyword in Python 2.6

> more f2.py
as = 1
import os
as = 3
> python f2.py
f2.py:1: Warning: 'as' will become a reserved keyword in Python 2.6

A quick look in parsetok.c reveals that it sets a "handling_import" flag
when it stumbles upon an "import" statement, a flag that's later used to
suppress the warning message.  The bug is that the flag isn't reset
until the parser sees an ENDMARKER token (end of file), instead of when
it sees the next NEWLINE token.

(if someone wants to submit this to bugs.python.org, be my guest)

I was wondering why I didn't have any warnings in my code in 2.5, when 
it started failing with errors on import in 2.6. Now I know.

Attaching patch and test.

I would be more comfortable if "started = 1" was also executed in the 
NEWLINE case. I'm not sure to understand the exact use of its value.

And do you think if it's possible to add the type==SEMICOLON case?
This would properly show the warning for:
    import sys; as = 3    # on the same line

There are still some far-fetched constructs that do not warn, like:
    import sys as as
but they are probably not worth the trouble.

You're right; I should put it within the started block. Actually, no
import cases are currently handled by the warning to avoid conflicting
with "import foo as bar". This isn't really an issue, though because
using the module name "as.attribute" will give a warning.

If we were going to do this again, I would implement the warning in AST
generation, but it's far too late for that.

Patch is good to me.

Actually 2.5 is not in "Release Candidate" stage, do we really need
formal review?

On Thu, Sep 25, 2008 at 2:46 AM, Amaury Forgeot d'Arc
<report@bugs.python.org> wrote:
>
> Amaury Forgeot d'Arc <amauryfa@gmail.com> added the comment:
>
> Patch is good to me.
>
> Actually 2.5 is not in "Release Candidate" stage, do we really need
> formal review?

Well, it certainly can't hurt. :)
>
> ----------
> keywords:  -needs review
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue3936>
> _______________________________________
>

Fixed in r66618.