-
-
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 #83
Comments
Hello, thanks for the report! I was able to replicate. The issue is again with wildcard imports. They're a PITA to handle 😅 Supporting wildcard imports as well as Python itself through inference will require quite important changes in Griffe. This won't happen very soon 🙂 But I'll add a way to fallback on introspection for such difficult cases. Also note that you can still use latest mkdocstrings with the legacy Python handler: just depend on |
I know it's been long since you opened this, but if you get the chance, could you try to build your docs using griffe's |
I found the contribution guide. I have had a try, and the doc looks fine :) |
Thank you very much for trying and reporting back! For potential future readers: you can install a Python package from a remote Git repository and a particular branch with:
|
I'll go ahead and close this, don't hesitate to open a new issue if it happens again 🙂 |
Hi, this issue did happen again. 😂 Still the same issue which causes infinite recursion on the same lines. Opening a new issue. |
Describe the bug
I went into infinite recursion after upgrading
mkdocstrings
to 0.19, which begins to use griffe.The stack trace is very long. Its first part is as below:
The full log is at here.
To Reproduce
I went into this issue for my Github repo. You can build the document following the guide. Please let me know if this requires too much effort, and I may try to provide a minimal reproduction.
Expected behavior
The doc should be built.
System (please complete the following information):
griffe
version: 0.20.0The text was updated successfully, but these errors were encountered: