Releases to pypi.org fail because of a direct dep (zaza)

[Alvaro Uria]

When doing the following, PyPI denies the upload because of direct dependencies (zaza, zaza-openstack):

$ make release
$ twine upload dist/*
Uploading distributions to https://upload.pypi.org/legacy/
Uploading juju_verify-0.1-py3-none-any.whl
100%|███| 44.1k/44.1k [00:01<00:00, 39.7kB/s]
NOTE: Try --verbose to see response content.
HTTPError: 400 Bad Request from https://upload.pypi.org/legacy/
Invalid value for requires_dist. Error: Can't have direct dependency: "zaza @ git+https://github.com/openstack-charmers/zaza.git#egg=zaza ; extra == 'dev'"

This issue was also reported here:
https://github.com/pypa/pip/issues/6301

Note: There are no pip packages for those 2 libraries.

[Robert Gildein (rgildein)]

After a long search, I found the following four options:
  - define dependencies in tox.ini
  - create a post install function in setup.py [1]
  - exclude extra_requires in setup.py [2]
  - ask the OpenStack team to release zaza on pypi

I think the best approach would be to use the tox.ini for extra dependencies or exclude extra_requires.

---
[1]: https://pastebin.ubuntu.com/p/sp5YG7ZZrX/
[2]: https://pastebin.ubuntu.com/p/Xvm3rGsX9v/

[Robert Gildein (rgildein)]

MP: https://code.launchpad.net/~rgildein/juju-verify/+git/juju-verify/+merge/403554