On Wed, May 2, 2018 at 4:58 PM, Oliver Bestwalter <oliver@bestwalter.de> wrote:
Hello Fred,
you are entering this on the deep end and there is a lot of things that might yield interesting results, so you are definitely not doinng something ridiculous, but a lot of unusual things and some things that give me the feeling that the tox docs need some serious TLC :)
Yeah, well, tox and every other testing and packaging tool for Python. :-) Thanks for taking the time to respond! I'm not (yet) sure what's requiring pbr; that's indirect.
Just shooting a few things from the hip here without having time to look in more detail, but I will try to give you some pointers:
The main red flag for me is pbr. Never having used it myself - I have no idea what it is doing exactly and how that might interfer with tox and "normal" virtualenvs, but I can remember dimly reading a discussion where someone struggled with getting this to work together with tox, so you should maybe first try to get some simpler project working without using pbr and then work your way up. The pbr folks use tox themselves, so if you are still running into problems them, mabye they might be better suited to help you.
Now for some more obvious things:
install_command = pip install -r tox-requirements.txt {opts} {packages}
should be:
deps = -rtox-requirements.txt
or even simper: listing the packages directly in tox deps instead of a special tox requirements file. Or you csan have the test deps as extras or tests_require as part of your setup.py. Read up about it here:
I've reduced this to: deps = kt.testing
Then:
basepython = /op/...all kind of interesting interpreters
basepython chooses the python that the venv should be built with, so you might have a different expectation here and I am not even quite sure what is supposed to happen here, as I never have played around with interesting basepython settings yet. So. Have a look at http://tox.readthedocs.io/en/latest/config.html#confval-basepython=NAME-OR-P... and decide for yourself and observe with tox -vvv what exactly is happening.
This seems to all be handled as expected; there are no visible references to the system Python (this is an Ubuntu 16.04 VM). I didn't see how else to tell tox where the Python interpreter was, and they're not on my PATH. Hence, [testenv:*] basepython.
Having the indexes in the requirements file is another interesting setting that I personally have never used. You can set the index also in tox, so maybe you want to experiment with that: http://tox.readthedocs.io/en/latest/config.html#confval-indexserver
I was avoiding that because of the deprecation warning, even though the doc doesn't point to an alternative. Also, currently using both --index-url and --extra-index-url. I should be able to create another index in my DevPI that combines my local packages and the root/pypi index. Something to try tomorrow. -Fred -- Fred L. Drake, Jr. <fred at fdrake.net> "A storm broke loose in my mind." --Albert Einstein