Skip to content
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

Version requirements on Markdown package? #2579

Closed
szhorvat opened this issue Jun 7, 2019 · 2 comments
Closed

Version requirements on Markdown package? #2579

szhorvat opened this issue Jun 7, 2019 · 2 comments

Comments

@szhorvat
Copy link

szhorvat commented Jun 7, 2019

I was not able to find any other support channel, so I am asking here. Please let me know if there is another place to ask (e.g. mailing list). The IRC channel is mostly dead in recent months and the channel logs are gone (so we can't check responses received when not logged in). Most of us can't afford to stay logged in continuously for 24 hours, or even for longer than a couple of hours.


Is there a list of requirements on the versions of dependencies, in particular the Markdown package? I am using Pelican 4.0.1. With Markdown 3.x, I see < converted to &lt; even in code blocks. With Markdown 2.x, everything is fine (so for now I simply downgraded).

Before I invest too much time into trying to debug this, it would be useful to know whether this is already known issue, and whether this is a problem Pelican or Markdown, or more likely an issue with my own setup.

@justinmayer
Copy link
Member

it would be useful to know whether this is already known issue

Hi Szabolcs. As mentioned in the How to Get Help section of the documentation, one of the best first steps is to check existing issues. It took me a matter of seconds to search for and locate the relevant existing issue: #2493

As noted in that thread, some folks report that the latest version (3.1.x) of Python-Markdown resolves the problem. If that's not the case for you, let's discuss potential resolution in the existing issue thread.

@szhorvat
Copy link
Author

szhorvat commented Jun 7, 2019

Thanks for pointing to that issue. My search attempts did not lead me to this one. I confirm that 3.1 fixes it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants