We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, I'm in the process of packaging this library for Debian (see https://bugs.debian.org/843882).
I noticed that ramlfications depends on markdown2 (https://pypi.python.org/pypi/markdown2, https://github.com/trentm/python-markdown2) rather than markdown (https://pypi.python.org/pypi/Markdown, https://github.com/waylan/Python-Markdown). It turns out that only the latter is packaged in Debian (https://packages.qa.debian.org/p/python-markdown.html). There are three solutions:
markdown2
markdown
ATM I took option 1, it was easy: https://gitlab.com/simevo/python-ramlfications/blob/master/debian/patches/0000-markdown2.diff. The only side-effect is that some tests fail for some silly newlines (which is also easy to patch: https://gitlab.com/simevo/python-ramlfications/blob/master/debian/patches/0001-test_newlines.diff).
Is there any specific reason why you depend on markdown2 rather than markdown?
The text was updated successfully, but these errors were encountered:
Bump ?
Sorry, something went wrong.
No branches or pull requests
Hi, I'm in the process of packaging this library for Debian (see https://bugs.debian.org/843882).
I noticed that ramlfications depends on
markdown2
(https://pypi.python.org/pypi/markdown2, https://github.com/trentm/python-markdown2) rather thanmarkdown
(https://pypi.python.org/pypi/Markdown, https://github.com/waylan/Python-Markdown).It turns out that only the latter is packaged in Debian (https://packages.qa.debian.org/p/python-markdown.html). There are three solutions:
markdown
only for the purpose of Debian packagingmarkdown
markdown2
in Debian as well (why not if there's a good reason).ATM I took option 1, it was easy: https://gitlab.com/simevo/python-ramlfications/blob/master/debian/patches/0000-markdown2.diff. The only side-effect is that some tests fail for some silly newlines (which is also easy to patch: https://gitlab.com/simevo/python-ramlfications/blob/master/debian/patches/0001-test_newlines.diff).
Is there any specific reason why you depend on
markdown2
rather thanmarkdown
?The text was updated successfully, but these errors were encountered: