Typogrify isn't found when Render Math is installed

[fpcorso]

I am encountering an issue when adding Render Math to a site.

Once installed, I then get this warning when I try to run Pelican to generate the content (it appears twice):

Typogrify is not installed, so it is being ignored. If you want to use it, please install via: pip install typogrify`

I already have Typogrify installed, and it is at least 2.0.7, as the readme says is required. I have tested both with 2.0.7 and 2.1.0. Additionally, I have TYPOGRIFY = True in my config file.

My site is fairly small, so I only have a few other packages installed:

anyio==4.4.0
beautifulsoup4==4.12.3
blinker==1.8.2
docutils==0.20.1
exceptiongroup==1.2.1
feedgenerator==2.1.0
idna==3.7
Jinja2==3.1.6
Markdown==3.8
markdown-it-py==3.0.0
MarkupSafe==2.1.5
mdurl==0.1.2
ordered-set==4.1.0
pelican==4.11.0
pelican-render-math==1.0.4
pelican-seo==1.2.2
pelican-sitemap==1.1.0
Pygments==2.18.0
python-dateutil==2.9.0.post0
pytz==2024.1
rich==13.7.1
six==1.16.0
smartypants==2.0.1
sniffio==1.3.1
soupsieve==2.6
typing_extensions==4.12.2
typogrify==2.1.0
tzdata==2024.1
Unidecode==1.3.8
watchfiles==0.22.0

[justinmayer]

Hi Frank. I was able to reproduce the issue, which I believe is unrelated to Typogrify. Before testing to see if Typogrify can imported, I believe the current code tries (and fails) to import packaging in order to determine whether the installed version of Typogrify is 2.0.7 or above.

Potential solutions could include:

1. Add packaging as a dependency to this project.
2. Compare version numbers without using packaging (or adding other dependencies).
3. Remove the version-checking code.

I imagine the second and third options would be preferable to adding another dependency just to check version numbers.

I think removing the version check would be fine, because Typogrify 2.0.7 was released over a decade ago in 2014, and there is not much likelihood that folks would be using older versions at this point.

@fpcorso: Would you like to help out by taking one of the above two approaches in the form of a pull request?

[fpcorso]

@justinmayer Yeah, that section of the code looks straightforward enough that I think I can work on a PR for this. Though it likely won't be for at least a few days until I get back to this 😅