-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
No new release to PyPI #133
Comments
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗 |
👍🏻 Really interested as well. |
@tsibley have you tried using the |
Ha, no, I hadn't tried. Oy vey. |
Catches warnings earlier during local builds, instead of only during CI. sphinx-autobuild doesn't have a released version which supports --keep-going¹, so be a little looser there. These options aren't the default for SPHINXOPTS so that that variable may still be used for passing additional options without unintentionally (and unnecessarily) overriding the strictures. ¹ <sphinx-doc/sphinx-autobuild#133>
I came here to request that
--keep-going
be added to the options passed thru tosphinx-build
, only to see it was already added in #109 (opened two years ago, merged ~6 months ago). That's great! But there's been no new release to PyPI for over two years. Would you please consider cutting a new release for the--keep-going
fix and other small fixes since the last release? Thanks for this very handy tooling!The text was updated successfully, but these errors were encountered: