Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add instructions to
HACKING.md
for how to test your local development version of this tox plugin in tox.I don't think it makes sense to try to make this any easier (for example by trying to wrap the whole thing in a convenient
make
command): we only maintain a few tox plugins and they're all really simple ones that hopefully won't require much ongoing development. Maybe we can try just living with manual instructions for this inHACKING.md
for now.Once we merge this I'll add the same to the
tox.ini
files of tox-faster and tox-envfile. We could add this to thepypackage
cookiecutter but it only applies to tox plugins so we'd have to add atox_plugin
boolean setting tocookiecutter.json
(similar to other boolean settings likeconsole_script
). Might not be worth adding this to the cookiecutter since it only applies to tox plugins?