Sublime Forum

Has 'pymdownx' library been removed from Package Control?

#1

Has ‘pymdownx’ been removed from Package Control? If so, how would I go about deploying it locally?

I have a ST plugin that I have authored locally. It has been working flawlessly until now.
It is now throwing the error: ModuleNotFoundError: No module named 'pymdownx'

I have the following dependencies.json:
{ "*": { "*": [ "bs4","soupsieve","lxml","pymdownx"] } }

I have run ‘satisfy packages’ and ‘satisfy libraries’ then restarted - no success.

When I browse Package Control Rs libraries, I now see this:

image
image.png2168×998 128 KB

Does that mean ST cannot resolve this library? Is there any way for me to deploy it manually?
Any help greatfully received

Here is the full error:

Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/Lib/python313/sublime_plugin.py", line 1637, in run_
    return self.run(edit)
           ~~~~~~~~^^^^^^
  File "/Users/gbird/Library/Application Support/Sublime Text/Packages/MD-to-Quiz/MD-to-Quiz.py", line 19, in run
    soup = md_parser(buffer_text)
  File "/Users/gbird/Library/Application Support/Sublime Text/Packages/MD-to-Quiz/MD-to-Quiz.py", line 751, in md_parser
    html = markdown.markdown(md, extensions=extensions, extension_configs=configs)
  File "/Users/gbird/Library/Application Support/Sublime Text/Lib/python313/markdown/core.py", line 481, in markdown
    md = Markdown(**kwargs)
  File "/Users/gbird/Library/Application Support/Sublime Text/Lib/python313/markdown/core.py", line 126, in __init__
    self.registerExtensions(extensions=kwargs.get('extensions', []),
    ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                            configs=kwargs.get('extension_configs', {}))
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/gbird/Library/Application Support/Sublime Text/Lib/python313/markdown/core.py", line 179, in registerExtensions
    ext = self.build_extension(ext, configs.get(ext, {}))
  File "/Users/gbird/Library/Application Support/Sublime Text/Lib/python313/markdown/core.py", line 225, in build_extension
    module = importlib.import_module(ext_name)
  File "./python3.13/importlib/__init__.py", line 88, in import_module
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1310, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 488, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1324, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'pymdownx'
0 Likes
#2

A quick follow-up. After a slight meltdown when all of the ST packages I had built and relied on stopped working, I ended up downgrading from Sublime Text Build 4202 (PRIVATE BETA) to the latest stable.

The missing libraries were satisfied and everything started working again. Not sure the root cause, but I am no longer seeking a solution.

Leaving this thread here anyway, just in case others have a similar experience

0 Likes
#3

Package Control 4.2.4 introduces a mapping of legacy dependency pymdownx to its official pypi name pymdown-extensions. This change should be transparent, but maybe you were hit by temporary transition issues.

PC automatically translates pymdownx to pymdown-extensions before looking it up in official registry for backward compatibility reasons. New plugins should however use the new name.

This should however not affect how modules are imported.

This issue is unrelated with ST version.

0 Likes
#4

Interesting. For whatever reason, downgrading back to 4200 resolved things immediately for me. Given what you say, was this just a happy accident?

Either way, everything is working again which is a tremendous relief.

0 Likes