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
Update sphinxify usage #13503
Update sphinxify usage #13503
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @martinRenou ; this should fix what Darker is complaining about.
Darker is actually not being run, there seems to be an issue with darker itself.
This has been reported here akaihola/darker#264 EDIT: This should be a workaround #13504 |
SHould this need to be backported to 7.x ? |
Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>
Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>
Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>
@Carreau yes it would be nice to backport it :) Thanks! |
How do you backport? Do you not use the meeseeks command? I tried looking at an example of backporting like #13427, does adding to the right milestone trigger the bot? |
yes, the milestone descriptions have commands to be ran by the bot, |
Really nice |
…503-on-7.x Backport PR #13503 on branch 7.x (Update sphinxify usage)
Docrepr 0.2.0 is out, with compatibility updates with "new" sphinx versions (it was not working with sphinx>=2). This PR uses that latest docrepr versions for generating the HTML doc representation.