packaging: poetry

[iancleary]

setup.py allows installation from development branch on github

Or, install from the development branch:

$ pipenv install -e git+https://github.com/taoufik07/responder.git#egg=responder

flit allows for more straightforward publishing to pypi with and without travis

[iancleary]

Perhaps I can have both in the template - I am not sure if cookiecutter allows optional files.

Situations where I see the setup.py route being useful is for inside organizations or when you want to allow installation directly from the git server, as that requires a setup.py file (which flit on generates at runtime during flit publish's sequence

[iancleary]

#11 adds a setup.py file for the Makefile to use.

[iancleary]

Copy over updates from https://github.com/iancleary/fastrf/ for both Netlify docs and Flit

Requirements.txt and runtime.txt

This allows Netlify to build the docs, and is not for fastrf developmen.

These are required to configure Netlify's deployment and pull request previews for mkdocs

Requirements.txt

https://docs.netlify.com/configure-builds/common-configurations/#mkdocs

Runtime.txt

Specifies python version for Netlify

< https://docs.netlify.com/configure-builds/manage-dependencies/#python>

[iancleary]

Need to remove pipenv as well

[iancleary]

Going forward with Poetry

[iancleary]

Closing per successful merge of #13