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

why markdown2 rather than markdown #119

Open
simevo opened this issue Nov 20, 2016 · 1 comment
Open

why markdown2 rather than markdown #119

simevo opened this issue Nov 20, 2016 · 1 comment

Comments

@simevo
Copy link

simevo commented Nov 20, 2016

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:

  1. I patch ramlfications to depend on markdown only for the purpose of Debian packaging
  2. you change ramlfications to depend on markdown
  3. we package 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 than markdown?

@simevo
Copy link
Author

simevo commented Feb 9, 2017

Bump ?

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