Python 3.x Compatibility Updates #2
Open
Conversation
This file contains hidden or 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
This PR contains commits for ultimately full Python 3.x compatibility. Some changes (such as formatting) may seem a little pedantic, but thats just who I am as a developer. The main thing in this isn't necessarily changing any API, mostly just to move towards Python 3.x in any library changes closer to that version. If you have any questions, comments, and concerns, please do let me know.
Author
|
Please don’t merge just yet as I’m still putting this PR together. |
Author
|
As well as still needing to actually test. |
…ptos'. Add pbkdf2 depend
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR contains commits for ultimately full Python 3.x compatibility.
Some changes (such as formatting) may seem a little pedantic, but thats just who I am as a developer.
The main thing in this isn't necessarily changing any API, mostly just to move towards Python 3.x in any library changes closer to that version.
If you have any questions, comments, and concerns, please do let me know.