-
Notifications
You must be signed in to change notification settings - Fork 12
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
extension with config data raises an error. #8
Comments
@MadLittleMods I know. I ran them. They failed when you include the extra config data inside quotes. If you look at the markdown docs it doesn't show the option. That's why I was wondering: could it be it is not supported anymore? Thinking further, should the current code be considered legacy and start a new plugin (or new version) supporting only the current version of markdown and python version>3.4 ? |
@sander76 Yes, it was only tested in older versions of Markdown and is why I asked you if it worked here, #6 (comment) |
@MadLittleMods I guess I was a bit quick on the conclusion. I have been using your plugin for a couple of years, but only with the "basic" configuration which works just fine. After I found out it worked for me I thought all was fine not really looking at the other options the plugin provides.... 🙄. So not sure how to proceed now... |
@MadLittleMods Sorry about this |
@MadLittleMods I am totally fine to create a trimmed down version of your plugin and giving you all credits. I don't think I can live up to the expectation of both keeping backwards compatibility, upgrading to the new markdown version and keeping all config options intact.... |
@sander76 We can create a new v3 branch for use with the latest Python markdown version Since it is a major version, it can have breaking changes |
@MadLittleMods Just checking: Has this ever worked?
Adding the
prefix=mypref-
raises an error with the latest version of markdown.The text was updated successfully, but these errors were encountered: