Work around spdx-tools assuming a "str" file instead of "unicode" #441

Merged
merged 1 commit into from Jan 11, 2017

Projects

None yet

2 participants

@sschuberth
Collaborator

No description provided.

@sschuberth sschuberth Work around spdx-tools assuming a "str" file instead of "unicode"
Fixes #436.
daf67e3
@pombredanne
Member

@sschuberth Thanks... let me review this. I had made only some quick tests and without keeping much history of it and only on Linux.

@pombredanne
Member

It is likely either because of https://github.com/sschuberth/scancode-toolkit/blob/daf67e313f0b47e39e911bd47782b8f9224b4322/src/scancode/cli.py#L28 and/or StringIO returning bytes and encoding OK in this case because of the default encoding.... Not so sure. But you should add some tests with and without non-ASCII content in the scans here to validate the behavior IMHO.

@pombredanne pombredanne merged commit 6458999 into nexB:develop Jan 11, 2017

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@pombredanne
Member

Thanks! we will still need some tests though ;)

@sschuberth sschuberth deleted the sschuberth:spdx-tools-unicode branch Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment