-
Notifications
You must be signed in to change notification settings - Fork 37
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
New intermediate release ? #53
Comments
Are there any alternatives to this plugin that are about as powerful? I am having increased issues due to this one not being further developed in my projects. Dependencies keep causing build issues and it's not feasible anymore to keep it up. I was wondering if anybody here has moved on to other plugins? |
In the mean time you could just use |
It seems there are not any alternatives at all. I was wondering if the developer @comwes still alive and breathing on the earth. For years this plugin has no new release for no reason and not a word heard from him. |
Hi, we are all in the same problem. I think the best option is for someone to fork and take care of pipy publishing new versions. Any interested? :D |
I can do that :D The best solution would be to have proper access to this repo and be a contributor here but it can be hard (@comwes any comment about that?). |
Although you may not be able to take over this repo without the owner's consent, you may fork it and become a maintainer of this fork. |
@flomnes That's the plan |
Ok, I've created a fork, made a few changes (seems to work with latest version of weasyprint) and published it to PyPI. Here you can find it: https://github.com/jurgenwigg/mkpdfs2-mkdocs-plugin ( https://pypi.org/project/mkpdfs2-mkdocs/ ). |
We would like to use this package for our project. However, version 1.0.1 does not seem to be compatible with mkdocs>=1.1 because of issues #14 / #16.
These bugs have been solved mid-2020. However, no release was made to included these fixes and many others.
Is it possible to publish a release including these fixes ?
It could be version 1.0.2.
The text was updated successfully, but these errors were encountered: