FS#28453 - [python-markdown] no support for python3, does not work

Attached to Project: Community Packages
Opened by Slo W. Poke (slowpoke) - Wednesday, 15 February 2012, 15:11 GMT
Last edited by Kyle Keen (keenerd) - Wednesday, 21 March 2012, 01:57 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:

python_markdown has no support for python3, and consequently doesn't work (Unicode vs Bytestring problems). It's a known issue[1] according to the github repository, but hasn't been fixed yet. In other words, this package is effectively not functional.

[1] https://github.com/trentm/python-markdown2/issues/64
This task depends upon

Closed by  Kyle Keen (keenerd)
Wednesday, 21 March 2012, 01:57 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 2.1.1-4
Comment by Lukas Sabota (punkrockguy318) - Tuesday, 06 March 2012, 12:05 GMT
I also experience issues with the python3 version of this: http://pastebin.com/TH4Zh2tA
Comment by Kyle Keen (keenerd) - Tuesday, 13 March 2012, 17:45 GMT
Upstream bug, so not really our problem. Nothing we can do.

Slowpoke, if you have any suggestion for how you'd like to see this resolved please make it. Otherwise I'll just delete the package.

Ángel, why did you create a package for something that was known to be completely non-functional?
Comment by Slo W. Poke (slowpoke) - Wednesday, 14 March 2012, 17:47 GMT
Hi keenerd,

I personally think deleting the py3 version of the package (for now) would be the best action to take, as well.

Providing completely non-functional software isn't a good idea if you ask me, especially if the issue is well known to upstream.
Comment by Angel Velasquez (angvp) - Friday, 16 March 2012, 15:42 GMT
@keenerd In theory no package depends of python-markdown but python2-markdown . and in theory wasn't completely non-functional as you've said, they've released this in order to get feedback from the community and and eventually will have the support.

So in order to have it as splitted you should comment that part on the PKGBUILD because eventually it will work and it will be used.

People who had python-markdown installed before this was pointing to python2 version so you can add a replaces on python2-markdown package.
Comment by Kyle Keen (keenerd) - Friday, 16 March 2012, 16:18 GMT
I think there is a little more going on. Debian and Fedora both carry this package, and with the number of maintainers (and their standards) they probably would not release something horribly broken. Plus the error seems like the sort of thing that could be fixed with a few encode() calls. I'm going to look into it a bit deeper before deletion.
Comment by Kyle Keen (keenerd) - Wednesday, 21 March 2012, 01:57 GMT
After a bit of digging, turns out there was a quick one line fix. Patched and working in python-markdown-2.1.1-4.

Loading...