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

[Feature request] Move plugins in-tree #481

Open
za3k opened this issue Jul 30, 2024 · 0 comments
Open

[Feature request] Move plugins in-tree #481

za3k opened this issue Jul 30, 2024 · 0 comments

Comments

@za3k
Copy link

za3k commented Jul 30, 2024

I've been using python-markdown2, and they have an idea of "extras" which are included as flags. Basically the same thing as plugins. It works way better than in Turndown.

I think the reason is that, much like other systems like Linux, they keep development in-tree. Bugs like (#416 (comment)) could not happen with in-tree plugin development.

What do you think about importing and maintaining a copy the authoritative copy of plugins in-tree?

I realize as I ask this that, given the number of open PRs and issues, this might not be a positive move just right now, but maybe this request will make sense down the line when Turndown is a little more caught up on maintenance.

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

1 participant