Skip to content
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

Force UTF-8 encoding for opening test files #152

Merged
merged 2 commits into from
Aug 2, 2019

Conversation

roclark
Copy link
Owner

@roclark roclark commented Aug 2, 2019

In some cases (such as running tests in Visual Studio Code), the "open" function in Python uses the incorrect file encoding format which can cause errors. To combat this, the encoding format should be explicitly stated.

Signed-Off-By: Robert Clark robdclark@outlook.com

Clark and others added 2 commits August 2, 2019 11:58
In some cases (such as running tests in Visual Studio Code), the "open"
function in Python uses the incorrect file encoding format which can
cause errors. To combat this, the encoding format should be explicitely
stated.

Signed-Off-By: Robert Clark <robdclark@outlook.com>
On Windows platforms, the recommended location for virtual environments
is in the env directory. This should be ignored to not have all of the
virtual environment scripts and files polute the git workspace.

Signed-Off-By: Robert Clark <robdclark@outlook.com>
@roclark roclark added the bug Something isn't working label Aug 2, 2019
@roclark roclark added this to the Release 0.4.4 milestone Aug 2, 2019
@roclark roclark self-assigned this Aug 2, 2019
@roclark roclark merged commit 954f4d1 into master Aug 2, 2019
@roclark roclark deleted the patch/force-unit-test-encoding branch August 2, 2019 17:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant