The pytest-runner package is deprecated and its use is discouraged. See:
https://github.com/pytest-dev/pytest-runner/
> pytest-runner depends on deprecated features of setuptools and relies
> on features that break security mechanisms in pip. For example
> 'setup_requires' and 'tests_require' bypass pip --require-hashes. See
> also https://github.com/pypa/setuptools/issues/1684.
>
> It is recommended that you:
>
> - Remove 'pytest-runner' from your 'setup_requires', preferably
> removing the setup_requires option.
> - Remove 'pytest' and any other testing requirements from
> 'tests_require', preferably removing the setup_requires option.
> - Select a tool to bootstrap and then run tests such as tox
Running tests should go through the tox entrypoint.
- Call python with relative path (bin/python) to use venv python.
- Possibly positioning `install-venv` to be the default target.
- No need to factor out venv target.
- Add Makefile target ``make readme`` to run ``viewdoc``
- Reorg "More Info" sections
- Docs to the top
- Less doc links (folks can find more than installation & guides from documentation link)
- Add link to PRs
- Reorg link to pre-fork changes
- Remove nose-cov comment: we know from requirements.txt that nose-cov is required.
- Phony targets comment: who cares? We'll just keep listing them all for now. URL still helpful.
- Coverage report comment: I don't get it. Reformat and add "XXX" to draw attention from someone who does.
- Remove relative calls to pip, python (assume virtualenv activated or otherwise "safe" global env)
- Full define development and documentation requirements in requirements.txt
``make test-dep`` installs documentation dependencies too, hopefully that's not too annoying.
This means development process for documentation and code can begin with:
virtualenv .
source bin/activate
pip install -r requirements.txt
This Makefile completely automates my pre-release testing routine which typically occurs only in Python 2.7, but gives me a "good enough" view of the status quo.
