Python3 compatibility #85
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
|
Thanks a lot Jonas. Looking at the changes, they may break python 2 compatibility. So yes, please use a separate python3 branch so that we can work on it while the master branch still runs on python 2. |
|
Thank you @zaddach for your work! |
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.
Hi,
I've started a first attempt at Python3 compatibility for ViperMonkey. It's running currently working with one test document (.doc), but I'm sure that there are some strings I haven't converted to
bytesif you use different file formats (.docx, .xls, .ppt).If you would rather have this in a separate branch (e.g., python3), I can re-create the PR against that branch.
Addresses #69.