Vincent Philippon

I would suggest to go with a `pip-tools.cfg` file or something alike, rather than `tox.ini`. I feel like options in `tox.ini` should be about testing and such. Nice suggestion 👍

I haven't looked much at the `setup.cfg` file. If it's meant to be extensible for other tools like that, then that sounds more reasonable to me.

For the list of Leads, it can be seen on the Jazzband website, right here: https://jazzband.co/projects/pip-tools I've been mostly away from the project for a while, so I'll say right...

Hi @twig, This is actually a normal behaviour: `pip-compile`'s job is to find candidates that respects **all** constraints. In this specific case, you required `requests==2.18.4`, and `vero` requires specifically `requests==2.7.0`....

You might be interested to know that `vero v2.0.1` has unpinned `requests` to avoid unnecessary dependencies conflicts. Related issue: waveaccounting/vero-python/issues/26 Now, about that override option, let me present it this...

First @jcerjak, thanks for the PoC. If I get this right, the idea in your PoC is that when getting a conflict, with `--allow-conflicts`, we try again with the original...