Adapt to upcoming Sphinx 2.0

[jakobandersen]

Initial steps to adapt to the upcoming version of Sphinx (2.0).

[svenevs]

Thank you @jakobanderson this is really helpful! I was under the impression that we needed to switch to pytest in order for the tests to run / user the sphinx fixtures. But it appears this is not the case.

Does this supersede #410?

[jakobandersen]

I think the testing between the projects are completely independent, though from my limited understanding of Python tooling it may still be a good idea to switch to pytest at some point (the Sphinx PR for switching: sphinx-doc/sphinx#3302),

I should probably have described the PR dependencies and their context:

1. If Adapt to Sphinx 1.8 #410 looks ok for you, it can be merged immediately so Breathe works completely with a supported Sphinx version.
2. (optionally) I have some code simplifications that shifts functionality to using the core Sphinx support, and I think also fixes some bugs. They can be applied after Adapt to Sphinx 1.8 #410.
3. The upcoming Sphinx 1.8.4 probably doesn't require any updates, except for the Travis script.
4. After Sphinx 2.0 has been released (see 2.0.0 release plan sphinx-doc/sphinx#5950) then this PR can be applied. It includes Adapt to Sphinx 1.8 #410, so in a few months it will superseede it.
5. (optionally) More code simplifications (and bug fixes?).

[vermeeren]

Thanks a lot for all submitting all these patches. I have been rather busy for a while so my responses to Breathe-related things have been slow. PR #410 seems ok to me, so I'll merge it now.

Indeed long term the plan for an eventual Breathe 5 is to rewrite and/or refactor major parts of the sometimes overly complex logic and let Sphinx itself handle things cleanly. As you said I am sure this will fix several open bugs and quirks. Thanks again!

[jakobandersen]

If you trigger a rebuild in Travis it should(TM) succeed now that Sphinx 2.0 has been released.

[meeludwig]

Hi michaeljones,
maybe I have found a rather deep & simple isse, rather breathe and not sphinx or doxygen.
sphinx-doc/sphinx#6146
Thanks , michael

[jakobandersen]

Doh, nevermind, 2.0 is close to be released, but it will take a few more weeks.

[t-b]

@jakobandersen Can you push to trigger a build?

[jakobandersen]

Now I think the PR should be ready to merge :-)

[vermeeren]

Looks good to me. Just to make sure: merge this and release as v4.13.0?

[amirmasoudabdol]

I'm wondering if there is still an issue with this PR? I'm using it for a while and it works fine, it'd be nice to merge it and have a new version :-) If there is an issue, I'm happy to help btw.

[Milerius]

can we merge this ?

[vermeeren]

I have released v4.13.0 containing this fix, all should be good now.

[Milerius]

@melvinvermeeren is it ready in pip ?

[vermeeren]

@Milerius Should be up now, the upload was running at the time you posted.

[Milerius]

@melvinvermeeren Thank's a lot i made the upgrade