New issue 296: support tracking changes in requirements.txt without full rebuild
https://bitbucket.org/hpk42/tox/issues/296/support-tracking-changes-in
Maxim Kovgan:
h4. Use case:
during the development, you often switch between new and old requirements.
This currently forces the user to run `tox
New issue 297: Allow `setup.cfg` as an alternative configuration file
https://bitbucket.org/hpk42/tox/issues/297/allow-setupcfg-as-an-alternative
Peter Bittner:
(This issue comes from a comment in issue #185.) I'd love to see the tox
configuration living in `setup.cfg` too in general, as an alte
