-
-
Notifications
You must be signed in to change notification settings - Fork 11
Something wrong with our sphinx compatibility matrix after #14... #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Oh, should probably CC @Sraw |
....oh, our tests use |
Well, yep, you are right. After reviewing commit, I think this problem exists also before merging #14 as I just change I'm now trying to find a compatible way in |
Also adds testing on 3.7 Fixes python-triogh-15
I found a possible way. In
I haven't tested, I am going on it. |
@Fuyukai reports running into a strange crash: https://gitter.im/python-trio/general?at=5b6730c63a5a2d2f99f91e22
This seems to be an incompatibility between #14 and whatever version of sphinx she's using (which it sounds like is some kind of 1.6.x, though I haven't confirmed this).
When we merged #14, we thought that it worked with any sphinx 1.6.x or 1.7.x. First problem is, we didn't actually add a
>= 1.6
to this package'sinstall_requires
insetup.py
, whoops.Second problem: I'm not sure that
>= 1.6
is the right thing! @Fuyukai's problem seems to be with a 1.6.x release, and I just checked the latest 1.6.x release tag, and it doesn't have asphinx.pycode.parser
module: https://github.com/sphinx-doc/sphinx/tree/v1.6.7/sphinx/pycodeBut somehow our CI tests are passing on 1.6, but weren't on 1.5? Something weird is going on here.
The text was updated successfully, but these errors were encountered: