Pygments 0.3.x broken on CentOS 5.8 about pygments.rb

[tnm]

Hi — This test case is being run against Ruby 1.8.5?

[bootstraponline]

@riddley says a custom-compiled ruby 1.9.3p0

[tnm]

I'll look into it. Thanks for the report.

Happy to help in any way I can.

[tnm]

@riddley — Can you let me know what version of python you are running on that machine?

Stock Centos 5.8 python 2.4.3

[tnm]

Ah! That is almost certainly the problem. We've never tested against python 2.4.x, and tbh we don't really support it, although patches are most certainly welcome. Even having support for 2.5 was a bit of a stretch :)

Is there anyway you can bump to 2.5?

We're due to migrate gollum to a newer Debian host soon. This will surely grease the skids.

Thanks for the help guys. Above and beyond!

[tnm]

Definitely, happy to help :)

[bootstraponline]

Thanks for the quick response @tnm. I'm closing this as won't fix but patches welcome. I've sent a pull request to add system requirements to the readme.

[VoldemarLeGrand]

In my case the problem was due to broken installation of alternative Python 2.6 on RHEL 5: the installer created executables python and python2.6 but not python2. Latter still point to old system version 2.4. All 3 executables were declared in $PATH: 2.6 directory with python and python2.6 first and then system directory /usr/bin with python2. So python command launch Python 2.6 while python2 launch system Python 2.4.

But actually popen.rb search for executable named python2 to launch mentos process. So in my case the old version was used despite correct version of Python was in the $PATH.

Workaround is to create virtualenv directory with all 3 possible executables.

Hope this can help someone.