-
Notifications
You must be signed in to change notification settings - Fork 57
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
Add projects from Python-Markdown's wiki #134
Conversation
Super nice checks in CI. Some extensions indeed do not provide a Python-Markdown entrypoint, I wasn't sure if it is still able to load them with the path of the module containing the |
Ha, the bugzilla extension uses old relative imports (without leading dots), so I suppose it wouldn't even work. I'll remove it. |
Would be nice if the CI report could show links to the repositories 🙂 |
What does "Also not found as a direct import." mean? For example Semantic Data packages a |
Looking at the code, I see that a simple search for from griffe.loader import GriffeLoader
loader = GriffeLoader(search_paths=[directory])
loader.load_module(base_path)
loader.resolve_aliases()
if "makeExtension" in loader.modules_collection[base_path].members:
break That doesn't explain why |
@pawamoy |
Yep, just saw that! Pushed a fix |
What kind of change does this PR introduce?
Description:
#128
I used the
markdown
category and label everywhere. Maybe at some point we'd want to better categorize markdown extensions. I didn't verify if the old extensions work with recent versions of Python-Markdown.Checklist:
README.md
file. Projects are only supposed to be added or updated within theprojects.yaml
file since theREADME.md
file is automatically generated.