-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Stub Files and Wildcard Expansion issues #79
Comments
Hi, thanks for the report!
After having taken a look at your logs (thanks!), I'd rephrase that to say that I forgot to take aliases into account when merging stubs. We should not try to resolve aliases when merging stubs. About the second issue: yup, it has been reported in #72 as well. I need to check why these aliases don't have a line number. A quick check of the code just told me that I never instantiate an alias without line numbers, at least not when visiting (when inspecting, yes, of course, since there's no line number information). That's one more reproducible example for me so, thanks 🙂 I'll try to get to it soon. Eventually, if it's not fixable, your "dumb fix", which is not dumb, will probably be applied 😄 |
Ah, maybe found a patch, if you could try it: for new_member, alias_lineno, alias_endlineno in expanded:
overwrite = False
already_present = new_member.name in obj.members
if already_present:
old_member = obj[new_member.name]
old_lineno = getattr(old_member, "alias_lineno", old_member.lineno)
overwrite = alias_lineno > old_lineno
if not already_present or overwrite:
obj[new_member.name] = Alias(
new_member.name, new_member, lineno=alias_lineno, endlineno=alias_endlineno
) |
Unfortunately unsuccessful
|
…d attribute Issue #72: #72 Issue #79: #79 Issue mkdocstrings/mkdocstrings#438: mkdocstrings/mkdocstrings#438
This should now be fixed by 0.20.0! Thank you for the report and help! Let me know if you still encounter issues 🙂 |
Im still showing this as an issue with griffe 0.20.0 relevent versions:
|
|
Oh yes, that's another issue. Will reopen until it's fixed. |
Apologies for bumping this, do you know when you'll have chance to fix this? |
I'll try to push a fix soon 🙂 |
Hey @LordOfPolls, sorry for the long wait. I've been busy / suffering from burnout. |
I just built NAFF's docs on master branch without any issues, please open a new issue if you still have encounter errors. |
Describe the bug
Griffe seems to be unable to resolve builtins in stub files - https://pastebin.com/JsqPWvZn.
The error seems to be occur within these 2 files
https://github.com/NAFTeam/NAFF/blob/master/naff/client/utils/attr_utils.pyi
https://github.com/NAFTeam/NAFF/blob/master/naff/client/utils/attr_utils.py
Upon deleting the
pyi
file to bypass the error, another error occurs (https://pastebin.com/CHYvChzD). I resolved this by adding a dumb-fix togriffe/loader.py[260]
allowing my docs to build successfully.To Reproduce
clone https://github.com/NAFTeam/NAFF
mkdocs build
Expected behavior
Docs build successfully
Screenshots
exceptions
griffe.exceptions.AliasResolutionError: Could not resolve logging
:https://pastebin.com/JsqPWvZn
TypeError: '<' not supported between instances of 'NoneType' and 'int'
:https://pastebin.com/CHYvChzD
System (please complete the following information):
griffe
version: [e.g. 0.2.1] 0.19.3Additional context
We've previously had issues building docs with mkdocstrings new parser mkdocstrings/mkdocstrings#382
The text was updated successfully, but these errors were encountered: