Skip to content

Fixed issue with wrong file mode for python3#2351

Merged
sphuber merged 1 commit into
provenance_redesignfrom
fix_migration_py3_integrity_violation
Dec 14, 2018
Merged

Fixed issue with wrong file mode for python3#2351
sphuber merged 1 commit into
provenance_redesignfrom
fix_migration_py3_integrity_violation

Conversation

@muhrin
Copy link
Copy Markdown
Contributor

@muhrin muhrin commented Dec 14, 2018

The log file to report an integrity violation was not correct and would
complain about expecting a bytes type instead of str. Fixed by setting
the mode to w+.

The log file to report an integrity violation was not correct and would
complain about expecting a bytes type instead of str.  Fixed by setting
the mode to w+.
@muhrin muhrin requested a review from sphuber December 14, 2018 11:56
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.003%) to 68.108% when pulling 60e3fa5 on fix_migration_py3_integrity_violation into bd91e88 on provenance_redesign.

1 similar comment
@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.003%) to 68.108% when pulling 60e3fa5 on fix_migration_py3_integrity_violation into bd91e88 on provenance_redesign.

@sphuber sphuber merged commit 53feb9a into provenance_redesign Dec 14, 2018
@sphuber sphuber deleted the fix_migration_py3_integrity_violation branch December 14, 2018 12:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants