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
Need to patch Python-Markdown for Cygwin #11
Comments
David, Your patch won't apply to the current code. In fact, this was changed back in 2.0.1. We are currently at 2.0.3 and closing in on a release of 2.1. Although, it does occur to me that you may have already upgraded. The problem there is that we renamed the script (we had multiple other problems which contributed to the rename) to |
Thanks for the reply!!! I'm glad it's being maintained, it looks really useful. No, I've only got version 2.0 installed. I followed the instructions at http://www.freewisdom.org/projects/python-markdown/Installation for *nix systems, and it told me to install version 2.0 (not 2.0.1), so that's what I did. It said that the github version was for people who wanted to live on the edge, and I wasn't looking for the edge :-). If you want people to use version 2.0.3, you need to fix the instructions at http://www.freewisdom.org/projects/python-markdown/Installation. I could edit that page, but I don't know if that's what you actually intend. Otherwise, people might follow the instructions :-). |
Ah, sorry about that. I just removed the specific version number from On Fri, May 27, 2011 at 12:44 AM, david-a-wheeler
\X/ /-\ `/ |_ /-\ || |
Python-Markdown does not work as delivered on Cygwin. It installs, but attempting to run it produces this error:
Traceback (most recent call last):
File "/usr/bin/markdown", line 44, in
from markdown import COMMAND_LINE_LOGGING_LEVEL
File "/usr/bin/markdown.py", line 44, in
ImportError: cannot import name COMMAND_LINE_LOGGING_LEVEL
The problem is that a Cygwin system is actually a Windows system underneath, so it requires the Windows patch. HOWEVER, sys.platform reports 'cygwin', not 'win32', so the patch isn't actually run. Just change the detection code so that 'cygwin' also enables the windows workaround, and all is well.
Here's a patch, please add it!
The text was updated successfully, but these errors were encountered: