Add poetry support; drop pipenv support; bump version

[dekoza]

No description provided.

[codecov]

Codecov Report

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

@@           Coverage Diff           @@
##           master     #544   +/-   ##
=======================================
  Coverage   98.95%   98.95%           
=======================================
  Files          19       19           
  Lines         670      670           
=======================================
  Hits          663      663           
  Misses          7        7           

---

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 a300b65...90bd931. Read the comment docs.

[tomwojcik]

Python3.9 is already released so it might be a good idea to add it to the tox file. Aside from that LGTM.

found something else

[tomwojcik]

I'm not experienced with poetry. I see that we now have redundant information in pyproject.toml and setup.py. Is it desired?

EDIT: I looked into it and it seems like you need to maintain setup.py if you want it to be installable via VCS. Otherwise setup.py can be removed. Is that correct? python-poetry/poetry#761 .

[dekoza]

Yes, setup.py can be removed. I overlooked it.

[haxoza]

I was a bit afraid that once we merge it then we will receive a bunch of issues (due to lack of setup.py) from people who pinned master branch in their requirements. However after many days it seems to be not a problem at all! 🎉

[dekoza]

Maybe that's because how setuptools (and pip) work right now - they respect build settings from pyproject.toml (PEP 518) and run appropriate builder (poetry-core in this case). Anyway, I'm glad too 😄