-
Notifications
You must be signed in to change notification settings - Fork 74
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
make pypff Python3 compatible #68
Conversation
This makes it hard for me to see what has changed.
Can you provide me with the error messages? Also know pypff is work in progress #2 |
Codecov Report
@@ Coverage Diff @@
## master #68 +/- ##
=======================================
Coverage 33.53% 33.53%
=======================================
Files 53 53
Lines 19454 19454
=======================================
Hits 6523 6523
Misses 12931 12931 Continue to review full report at Codecov.
|
Unfortunately not really. I do have this screenshot though. All the errors were along the same kind.
I saw that but assumed it stagnated as it's from 2014. Everything else works fine, just the setup script had errors.
True. Tried to fix it. Not sure if your interpreter is not as strict as mine, but I had to change some indentation, otherwise Python tells me, that the indentation is not all the same. |
Thanks, that is sufficient.
I have limited time to work on it.
I'll have a look to see what changed and make the changes manually. For your context setup.py is generated by https://github.com/libyal/libyal/blob/master/scripts/source-generate.py |
@TimRepke thanks for the proposed changes though I'll not directly merge this PR. Since setup.py is generated elsewhere and this PR will need some clean up. I'll incorporate the necessary changes and regenerate setup.py for libpff. Tracking changes to setup.py in libyal/libyal#63 |
Adopted version of proposed changes integrated into fecb691 |
I constantly got errors by setup.py during installation of the package. After these changes (sorry, my IDE messed with the indentation) things worked for me using Python 3.6.6
Essentially, Python 3 handles str/bytes differently, that's all