-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Infinite recursion in griffe (again) #122
Comments
😱Thanks for the report, will try and replicate now 🙂 |
Griffe 0.25.1 should fix it 🙂 |
Sorry for the late response. The infinite recursion erorr did disappear, but no API is rendered. The result is only an empty page. I have tried both Griffe 0.25.1 and 0.25.5, with other dependencies kept to the latest. Please still use the repo mentioned in #83 to reproduce. The specific commit I tried is roastduck/FreeTensor@63cd89f . Only the old |
That's alright! Thanks for reporting :) Good to hear this is fixed. Now you're probably just missing the |
Tested with Griffe 0.25.5. Feel free to open a new issue if you like. |
One day it will work maybe 🤣 Thanks for the update, I'll investigate :) |
It's again because of wildcard imports (which Griffe does not handle perfectly, for various reasons).
I think I've been able to add a guardrail against this case. I'll push a fix soon after I verified this is working properly. |
Will close now, keep opening issues if you have any 🙏 ❤️ |
See #83. Still the same problem.
No infinite recursion with
griffe==0.23.0
orgriffe==0.24.0
, but failed withgriffe==0.25.0
. Latest compatible versions ofmkdocstrings[python]
is resolved bypip
accordingly.Even when using
griffe==0.23.0
orgriffe==0.24.0
, it only renders an empty API doc page. I remember the rendering was fine when I was testing against the PR branch then. There might be some differences between the PR branch and the 0.23.0 release, or the difference version ofmkdocstrings
causes the problem, or perhaps there was something wrong when I did the testing.The text was updated successfully, but these errors were encountered: