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
Problem with missing has_key in Python 3.0+ #3
Labels
Comments
hugsy
pushed a commit
that referenced
this issue
Apr 7, 2015
* dict.has_key(k) -> k in list( dict.keys() ) * dict.iteritems() -> dict->items()
Fixed by 0bd1ef5. Thanks for report 👍 |
hugsy
pushed a commit
that referenced
this issue
Apr 8, 2015
This was referenced May 3, 2018
This was referenced May 14, 2018
Closed
SakiiR
pushed a commit
to SakiiR/gef
that referenced
this issue
Jul 1, 2019
* dict.has_key(k) -> k in list( dict.keys() ) * dict.iteritems() -> dict->items()
SakiiR
pushed a commit
to SakiiR/gef
that referenced
this issue
Jul 1, 2019
* from __future__ statement
SakiiR
pushed a commit
to SakiiR/gef
that referenced
this issue
Jul 1, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a couple of instances in GEF of calls to dict.has_key(), which was removed in Python 3.0.
Changing those to "xxx in dict" rather than "dict.has_key(xxx)" seems to fix the problem and should be backwards compatible.
The text was updated successfully, but these errors were encountered: