New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faulty suppression of 'as' keyword warning #48186
Comments
Copied from c.l.p post by F. Lundh > >>> 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:
A quick look in parsetok.c reveals that it sets a "handling_import" flag (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 |
Attaching patch and test. |
I would be more comfortable if "started = 1" was also executed in the And do you think if it's possible to add the type==SEMICOLON case? There are still some far-fetched constructs that do not warn, like: |
You're right; I should put it within the started block. Actually, no If we were going to do this again, I would implement the warning in AST |
Patch is good to me. Actually 2.5 is not in "Release Candidate" stage, do we really need |
On Thu, Sep 25, 2008 at 2:46 AM, Amaury Forgeot d'Arc
Well, it certainly can't hurt. :)
|
Fixed in r66618. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: