FS#22988 - [python-pygments] Provide python- and python2-pygments

Attached to Project: Community Packages
Opened by Øyvind Heggstad (Mr.Elendig) - Monday, 21 February 2011, 15:05 GMT
Last edited by Stéphane Gaudreault (stephane) - Wednesday, 23 February 2011, 19:01 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Pygments have been ported to python 3.x, and it would be nice to have it for both 2.x and 3.x

http://pygments.org/faq/#python3

This task depends upon

Closed by  Stéphane Gaudreault (stephane)
Wednesday, 23 February 2011, 19:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  python-pygments-1.4-3 is in [community-testing]
Comment by Angel Velasquez (angvp) - Tuesday, 22 February 2011, 05:38 GMT
Ok Thomas please assing the correct maintainer next time .. assigning this to Evangelos
Comment by Stéphane Gaudreault (stephane) - Tuesday, 22 February 2011, 14:52 GMT
I suggest to wait after the python 3.2 rebuild to do this.
Comment by Evangelos Foutras (foutrelis) - Tuesday, 22 February 2011, 15:17 GMT
Good idea, Stéphane. I'll wait until Python 3.2 hits [testing] and will push the new packages to [community-testing].
Comment by Evangelos Foutras (foutrelis) - Tuesday, 22 February 2011, 19:50 GMT
I pushed the new packages to [community-staging]. I also rebuilt three packages to use the correct name in their dependencies: bpython, python-cheetah, and python-sphinx.

I've put all these packages in the todo list, marked as complete, so they can moved to [community-testing] along with the rest.

Also, adding (and subsequently removing) the maintainers of the three packages I modified to this bug's assignees, so they know why I messed around with their packages. Hopefully, they won't get mad. :>

Loading...