Closed nehalecky closed 9 years ago
You should use and contribute to knitpy, not pymarkdown. Pymarkdown was a single weekend toy project, is far less mature, and is not maintained. On Aug 11, 2015 6:48 AM, "Nicholaus Halecky" notifications@github.com wrote:
Hello!
As I have been investigating tools in this area, just wanted to point out the pymarkdown https://github.com/mrocklin/pymarkdown project by @mrocklin https://github.com/mrocklin as seems like there both have the same goal? Apologies in advance if I am overlooking an existing discussion that already covered this or if I am overgeneralizing the goals of each project.
So awesome to see this effort, hope to contribute soon. :)
— Reply to this email directly or view it on GitHub https://github.com/JanSchulz/knitpy/issues/30.
Thanks @mrocklin for reply, appreciated. Should we consider any particular functionality from pymarkdown that you think beneficial for this project?
Not really. It was a pretty ugly hack.
Refreshing straightforwardness—thanks. For a weekend project, nice work. I also appreciate the documentation.
So, it seems like the community will be making camp here at knitpy for the time being. :)
What will you do with pymarkdown? Perhaps we should try and redirect interest to this project? (brief history: I came across pymarkdown first and had cloned it to begin exploring).
@mrocklin: Thanks, this was perhaps my fastest issue resolution. Closing.
Hello!
As I have been investigating tools in this area, just wanted to point out the pymarkdown project by @mrocklin as it seems like they both have the same end goal? Apologies in advance if I am overlooking an existing discussion that already covered this or if I am overgeneralizing the goals of each project.
So awesome to see this effort, hope to contribute soon. :)