-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
[Doc] Add troubleshooting guide about pkg_resources module not found error #46208
[Doc] Add troubleshooting guide about pkg_resources module not found error #46208
Conversation
…error Resolves: ray-project#46205 Signed-off-by: Chi-Sheng Liu <chishengliu@chishengliu.com>
@kevin85421 Can you help me review this PR? Thanks. |
Thank you for filing the issue and making this PR! @peytondmurray @can-anyscale, would you please review? |
@MortalHappiness What version of Python are you running? I feel like I saw this with 3.12 and I'd prefer not to merge this as is, because the use of
|
i have seen this error with python 3.12 with other libraries as well; perhaps we can change the instruction to use python 3.11; i get a feeling that many packages out there doesn't work seamlessly with python 3.12 yet (or our requirements-doc.txt doesn't) |
but agree, |
I'd still vote to just bump the version or remove the extension. Active support for 3.11 has already ended months ago, so we should really be on 3.12 at the moment IMO, especially since the fix is so straightforward 🤷 |
My python version is 3.12. Actually the newest version of Line 13 in 9e1d4fe
See https://github.com/sphinx-contrib/redoc. It has not been updated for 4 years. Therefore |
Maybe the right way to go then is to drop |
how much work will that be @peytondmurray? |
Probably not much - I'll build on a separate branch and send a screenshot to you and @angelinalg in a few minutes. |
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.
put back to your queue since the doc team is thinking about solving this in a different way; thanks for bring this up issue
Closing this, as it has been resolved by instead updating the doc build requirements in #46208. |
Why are these changes needed?
See the description in the corresponding issue for details.
Related issue number
Resolves: #46205
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/
under thecorresponding
.rst
file.