Fix bug in setup.py

[whzup]

Description

Fixed a bug in the setup.py file where it would throw an error because the encoding format was not right. This is done by adding the encoding parameter to the open() function.

Related Issue

Resolves #174

Motivation and Context

There might be users that cannot install the package using the setup.py file because of that.

How Has This Been Tested?

I ran the setup.py file.

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[ljvmiranda921]

While you’re at it, maybe we can add a Semaphore CI to test on Windows. Windows is terrible with UTF8 and some CRLF, etc. Might also be the cause of the problem

[whzup]

According to the docs:

There’s another group of encodings (the so called charmap encodings) that choose a different subset of all Unicode code points and how these code points are mapped to the bytes 0x0–0xff. To see how this is done simply open e.g. encodings/cp1252.py (which is an encoding that is used primarily on Windows). There’s a string constant with 256 characters that shows you which character is mapped to which byte value.

So Python might just take cp1252 as default decoding on Windows.
BTW, it also happens when I use Python 3.6.

[ljvmiranda921]

Copy that. Let's add continuous-integration on Windows on v.0.4.0