-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
griffe 0.25.1 errors with CyclicRedundancy on uuid
#123
Comments
Errr, fixing something and breaking something else 😅 |
Thankyou! Please let me know if there's anything I can do to assist with the process (testing etc). I started looking into it a bit more, and in terms of the dependency path, I realised there are actually two
This could potentially be the cause of the issue? If it were a single I will try updating that init in |
It did indeed remove that error - but another one appeared in its place for an import of
|
I've pushed the version with the modified import for |
Thank you for the investigation! That's really helpful. 90% of Griffe bugs come from wildcard imports indeed. They're a PITA to handle :/ I always recommend avoiding them, but I understand how convenient they might be. The way we handle indirections would probably benefit from a proper design as well. I've implemented it on top on the existing, simple data structures. Anyway, enough ramblings. Time to write proper tests for wildcard imports. |
Unfortunately due to the nature of our library, it's difficult to avoid, because we need to expose classes from the submodules as if they were part of the base module, and we have a model file that is generated by datamodel-code-generator, so it can change frequently and we always need to expose everything inside it. We have managed to limit the use of Keep me posted if there's anything else I can do :) |
Hi @digitaldogsbody, it seems I cannot replicate the issue anymore in your repository 🤔 |
I can replicate both the original issue (with griffe is 0.25.1 and
Running |
Ah, my bad, I forgot I had patched griffe in the venv itself yesterday. Thank you for helping me remember that :) Hopefully I won't bother you again until it's resolved :) |
Should be fixed in 0.25.2 (both cases, in your |
Happy to confirm the fix working here. Thanks so much for your speedy work on this, it's really appreciated. |
Describe the bug
Since moving from 0.25.0 to 0.25.1, previously building documentation started failing, with a
CyclicAliasError
pointing atuuid
.We are using
mkdocs >=1.4.0, <2.0.0
andmkdocstrings-python >=0.7.0, <1.0.0
, with the pythonshow_submodules
option enabled inmkdocs.yml
and a single "code" markdown file that points to the root of the library.The application code itself only contains a single include of the
uuid
library in one file, so I am not certain how there could be a cyclic issue.Forcefully pinning
griffe==0.25.0
in the requirements makes the build succeed again, with no change to the application code.To Reproduce
Steps to reproduce the behavior:
pip install griffe==0.25.1
mkdocs build --strict
Expected behavior
The documentation should build successfully.
Screenshots
If applicable, add screenshots to help explain your problem.
System (please complete the following information):
griffe
version: [e.g. 0.2.1] 0.25.1Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: