The problem with this is that it's extremely brittle, particularly the replace() filter that removes -sqlite3 from the tox environment name if it exists. This is currently necessary because the py{2,3} environments are natively sqlite anyway. The tox file hasn't been designed with this vagrant image in mind.
I've tried to match up the database names with the aliases and settings module names with as little processing required. I don't think we can just reuse the sqlite name, because those settings already exist within the test/ directory. Perhaps the explicit PYTHONPATH will take precedence though?
As of 500668c9c70649c0bc5df364e1fdd5b7edd8b8af the ansible provisioner will now rely on tox from
/django
to provide virtualenvironments and requirements files for each environment. In an effort to avoid repetition I've generated each alias using nested variables: https://github.com/django/django-box/blob/500668c9c70649c0bc5df364e1fdd5b7edd8b8af/roles/python/tasks/main.yml#L62The problem with this is that it's extremely brittle, particularly the
replace()
filter that removes-sqlite3
from the tox environment name if it exists. This is currently necessary because thepy{2,3}
environments are natively sqlite anyway. The tox file hasn't been designed with this vagrant image in mind.I've tried to match up the database names with the aliases and settings module names with as little processing required. I don't think we can just reuse the
sqlite
name, because those settings already exist within thetest/
directory. Perhaps the explicit PYTHONPATH will take precedence though?