User: Password:
Subscribe / Log in / New account

Just curious

Just curious

Posted Feb 27, 2013 3:44 UTC (Wed) by mathstuf (subscriber, #69389)
In reply to: Just curious by HelloWorld
Parent article: Ruby 2.0.0 released

The project has Python bindings, not an embedded Python, so shipping our own isn't really an option[1]. To be fair, there is a 2.6 package for RHEL5, so that is a possible path. Also, the chance of the RHEL5-targeting project using the Python support is low, but I'd rather keep compatibility incrementally than as an all-at-once change. The test suite is where most of the code which hits this problem lives, and it's nice for code that doesn't ship to raise a lower version bound on something. Doesn't make it less painful.

[1]I suppose, technically, it is, but we also try to play nice with Python world by converting between NumPy and C++ data structures instead of forcing Python to use a C-like API. Losing that by trying to get an embedded Python to work with a non-embedded Python isn't worth it (or we ship NumPy too...). Unless I've missed some docs on that...

(Log in to post comments)

Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds