Unify setup.py name with package name

[christian-intra2net]

It is unusual for name and package name to be different. This complicates building rpms, for example.

[codecov-io]

Codecov Report

Merging #29 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #29   +/-   ##
=======================================
  Coverage   36.68%   36.68%           
=======================================
  Files          13       13           
  Lines        1145     1145           
=======================================
  Hits          420      420           
  Misses        725      725

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8689b89...34dc687. Read the comment docs.

[nolze]

Thank you for PR!

I totally agree that it would be better if we had the single name, but now I consider it is virtually impossible for several reasons:

• Thanks to a FreeBSD Ports maintainer antoine, msoffcrypto-tool is now available on the Ports as py-msoffcrypto-tool.
• MS-OFFCRYPTO is a specification under the control of Microsoft with a complex somewhat-open license. It seems that Microsoft is nervous even about the Python package names. It could be troublesome if we adopt the exactly same name with the spec.

I feel our situation is tolerable, as some well-known packages are named doubly as well. (e.g. scikit-learn and sklearn)
Please comment or open an issue if more detailed consideration is required.

[christian-intra2net]

Ok, those are valid reasons. Then we will have to live with it, I guess.