https://github.com/Arkq/flake8-requirements

After generating a new project from the template, running tox shows the warning below. Should the template be adapted?

check run-test: commands[0] | python setup.py check --strict --metadata --restructuredtext
running check
warning: Check: This command has been deprecated. Use `twine check` instead: https://packaging.python.org/guides/making-a-pypi-friendly-readme#validating-restructur

We have script for updating our requirements. But we can move to some better:

pip-compile development.in
pip-compile documentation.in
pip-compile production.in

i think this looks much better.

• remove check-requirements.py
• add pip-compile for upgrade command into makefile
• describe into the documentation how use *.in files for that

https://github.com/jazz

For example:

def main():
    set_python_version()
    # Initialise git repo
    os.system('git init')
    # Install dependencies
    os.system('pipenv install --dev')
    # Setup pre-commit and pre-push hooks
    os.system('pipenv run pre-commit install -t pre-commit')
    os.system('pipenv run pre-commit install -t pre-push')
    print(SUCCESS + "Project successfully initiali

Since version 2.0, Fabric has stopped providing fabric.api module and has changed its API organization.

Changelog: http://docs.fabfile.org/en/latest/upgrading.html#api-organization

fabfile.py should be restructured to use the new http://docs.fabfile.org/en/latest/api/connection.html#fabric.connection.Connection module.

Description

The starting README should have more than just a TODO.

Rationale

Leaving TODOs in committed code is a deprecated practice. Issues are the standard way of filing TODOs.

Use case(s) / visualization(s)

//: # ("Better to see something onc

Something like this