-
Notifications
You must be signed in to change notification settings - Fork 201
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
👌 IMPROVE: declare parallel read safe #225
Conversation
Thanks for submitting your first pull request! You are awesome! 🤗 |
ah yes - I suspect that it is as well. @chrisjsewell I feel like you have more experience w/ parallelism in Sphinx, any reason to think we can't set this to True? |
no it shouldn't be an issue, although of course you can always look to add a test case for parallel builds |
I added a test. It is very simple, but did find a problem in another extension. I tried, but was unable to add add it to pytest. You have to pass parallel=2 to the constructor of Sphinx, but I don't know how to pass it through. I have also tested on a 1500 page doc and it works fine. The force push was to cleanup the commits addressing ci issues. |
Yeh unfortunately it is not available via the test app: |
alright I think that we're all 👍 on the changes and tests are all happy, so I'm gonna merge this in. Thanks very much @rscohn2 !! much appreciated :-) |
Fixes dask#78 the upstream theme is also parallel safe this theme doesn't add any event handlers so must also be safe executablebooks/sphinx-book-theme#225
Fixes dask#78 the upstream theme is also parallel safe this theme doesn't add any event handlers so must also be safe executablebooks/sphinx-book-theme#225
I am getting this warning:
The PR declares the extension is parallel read safe, eliminating the warning and allowing parallel read.
I am not sure if the extension is parallel read safe, but it seems likely.