-
Notifications
You must be signed in to change notification settings - Fork 132
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
Markdown TypeError with Ford (markdown 3.4.1 related?) #437
Comments
Markdown 3.4 has removed a bunch of deprecated features, which has broken some extensions, including one we use by default, There is a PR fixing it: cmacmackin/markdown-include#34 The workaround for the time being is to do e.g. @cmacmackin If you'd like me to help maintain that repo as a key dependency of FORD, I'm happy to do that |
Ah. Thanks! I added: - name: Downgrade Python Markdown
run: pip install --upgrade "markdown<3.4" to my GitHub Action and it seems much happier now. (Though I might file a question about something else...) |
@ZedThree Thanks, I was just thinking of asking if you'd like to do that! I'll give you the necessary permissions. |
First, let me say this might not be a Ford error, but I figured I'd start here. So this morning I did a sync up of my repo where I'm playing with Ford (see #431 and all the other issues that @ZedThree has helped me with), and with that sync, my "Run Ford" GitHub Action sprang into action...and failed. The error I got was:
This very well could be due to my Ford config file as I am still fiddling around, but then I was looking at the Python Markdown repo and saw in the v3.4 changelog:
and GitHub did get Markdown 3.4.1:
As I said, I'm not sure if this is a Ford issue, or a Python-Markdown issue, or a me issue. I mean I added this:
to my Ford config file mainly because I saw other people using it in theirs. 😄
The text was updated successfully, but these errors were encountered: