'Extra' extension issue with pyinstaller #884
Comments
|
There are three ways to load an extension:
The way the third option works is that extensions are registered on install with a setuptools entrypoint. When Markdown receives a string, it checks for an entrypoint with the same name and, if it finds one, it uses it (if it fails, it then falls back to trying to import the string as an importable path). My assumption is that pyinstaller is not playing nice with entrypoints. Therefore, if you are using pyinstaller, you cannot use the short names for extensions. However, the |
|
I just remembered that we broke support for If we do anything, we probably should just deprecate the |
|
Thanks, seems reasonable and just including the full list of extensions in markdown.markdown isn't much of a burden. |
I posted this on stackoverflow because I thought it was a pyinstaller issue, but I'm wondering if it's really a python-markdown issue.
https://stackoverflow.com/questions/59052079/pyinstaller-and-python-markdown-importerror-no-module-named-extra
The text was updated successfully, but these errors were encountered: