Python 2.7 fixes #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
What's the problem with properties on old-style classes? I just tried defining one and it seemed to work. Is it a problem that doesn't become evident until runtime? I'd like to avoid switching this to a method if possible, since it's a backwards-incompatible change. Maybe we can just turn this into a new-style class? If there's no way to avoid the backwards-incompatible change, we at least need to call this version 2.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The only substantive changes are the removal of @Property decorators in old-style classes and replacement of property reads with method calls.
Unfortunately, my editor is set to remove white space at end of lines. Sorry about the noise.