Created attachment 305001 [details] patch allowing dev-python/markdown on Python >= 3.1 =dev-python/markdown-2.1.1 currently masks Python 3 via RESTRICT_PYTHON_ABIS="3.*" According to PyPI (http://pypi.python.org/pypi/Markdown), the module supports python 3.1 and 3.2 out of the box since 2.1.0.alpha. See http://freewisdom.org/projects/python-markdown/Tickets/000069 for details. Note that I could not find a commit 3db36d4 in the history of https://github.com/waylan/Python-Markdown, but commits f57dcb4b241c283fbe32694fa0d6729eaefe3e85 and 3b2820f23ea5088afbb1c76b9831e311a0b5bcd3 from January 2011 seem to fit the bill. I'm attaching a patch that works on my amd64 system, although this should be arch-agnostic.
This patch is insufficient for src_test(). See correct ebuild from Progress Overlay: http://code.google.com/p/gentoo-progress/source/browse/overlays/progress/dev-python/markdown/markdown-2.1.1.ebuild
(In reply to comment #1) > This patch is insufficient for src_test(). See correct ebuild from Progress > Overlay: > http://code.google.com/p/gentoo-progress/source/browse/overlays/progress/dev- > python/markdown/markdown-2.1.1.ebuild Good point about src_test(). There's all kinds of strange stuff in the progress ebuild. I found documentation for `EAPI="4-python"` in the Portage source, but it isn't mentioned in the Package Manager Specification. I'm not sure if that has any bearing on acceptance into the Portage tree. `PYTHON_DEPEND="<<[xml]>>"` also seems to be unique to the progress overlay's python.eclass. I don't really keep up with python.eclass development. Are there plans for merging these features into the Portage tree?
Fixed without a revbump.
