-
Notifications
You must be signed in to change notification settings - Fork 856
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
NameError when Parsing an Email Address #29
Comments
How did you install markdown? Was the 2to3 tool run on the source before installation? If I recall correctly the import path for html.entities is one of the Unfortunately, when we released Markdown 2.0.3 we had not yet set up On Mon, Jun 27, 2011 at 6:10 AM, sfstpala
\X/ /-\ `/ |_ /-\ || |
The Code I'm using comes from EnigmaCurry's repo. It's supposedly nothing more than 2.0.3 run through 2to3. Should I do it differently until the next release? On a side note: Perhaps you should remove the Python 3 tag from the PyPI entry until the usual installation works. Thanks a lot for the prompt reply. It's a big help, since I have this version of Python Markdown running on a production server. |
Ok, I just looked at the source (and EnigmaCurry's repo - interesting I didn't know it existed). The problem stems from a bug in the 2to3 tool which shipped with Python 3.0, which was the only version available when we shipped Markdown 2.0.3. That bug has since been fixed in Python 3.1. Unfortunately, the fix in the Python 3.1+ version of the 2to3 tool broke our workaround. As we have already fixed this in our repo (next release coming soon), I'd suggest filing a bug report with EnigmaCurry to fix the import in markdown/inlinepatterns.py line 48. Probably something like this (untested):
Regarding our claim to support Python 3.0. That is correct, Markdown 2.0.3 only supports (the buggy) Python 3.0, not 3.1 or greater. Therefore, I will not be changing our note in that regard. However, our next release will not support Python 3.0 but will support Python3.1 or greater. As there is no issue for use to fix here, I'm closing this. |
This is excellent, thanks a lot Waylan. Here's what I'm running now:
|
I'm getting a
NameError
when trying to parse an email address like this:Here's the complete traceback:
Links of the same format,
<url>
, work well.Hope this helps to solve the Problem. In the meantime, any workarounds would be appreciated.
This is Python Markdown 2.0.3 running on Python 3.2
The text was updated successfully, but these errors were encountered: