-
Notifications
You must be signed in to change notification settings - Fork 430
tox config is broken #339
Comments
I should add that the offending line is and the issue is a circular reference between |
This is a temporary workaround due to the config parsing change introduced in 2.2.0. See googleapis#339 for more details.
@jonparrott Any idea on how to fix this? (I did the "cowardly" thing and downgraded |
I accidentally stumbled on something which I think/hope will solve this: |
All I've got is to just wait. We ended up pinning tox in python-docs-samples as well. Consider tox isn't a direct dependency of library, pinning it for a while doesn't seem too offensive. |
I don't think waiting will work. I think we are permanently broken. I tried making the change suggested by my other PR and get a circular dependency sort of error: ...
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 959, in _replace_substitution
val = self._substitute_from_other_section(sub_key)
File "/usr/local/lib/python2.7/dist-packages/tox/config.py", line 944, in _substitute_from_other_section
(section, item), self._subststack))
ValueError: ('testenv', 'gae_pythonpath') already in [('testenv:gae', 'setenv'), ('testenv', 'gae_pythonpath'), ('testenv:gae', 'setenv')] It seems like it is getting a self-reference and it will "always" be impossible for |
@waprin who's more involved in the testing side than me. |
@jonparrott By forcing me to articulate that
I realized we could just ditch |
Haha JK:
|
It's a bug a lot of people are experiencing, people already have PRs to fix it, they are just in the process of getting vetted/merged: https://bitbucket.org/hpk42/tox/issues/285/tox-220-breaks-some-toxini-config-files |
w00t. Thanks @waprin |
This is no longer broken right? |
Failures noticed in #336 and #337.
From http://tox.readthedocs.org/en/latest/changelog.html it looks like the 2.2.1 release notes explain the failure
Seems https://bitbucket.org/hpk42/tox/pull-requests/169/tries-to-fix-99/diff is the PR that fixed something but broke us
The text was updated successfully, but these errors were encountered: