|On a historical note, Perl and Python were the original candidates for Blender's scripting language. The Perl guys failed to make their case.
Embedding an interpreter is fairly trivial. The problem is the work that has to be done to support it. There are two main parts to this:
- generating the language bindings
- writing all the glue code.
For the first one, New Blender has its DNA/RNA system which is used to help generate the Python bindings programmatically. This should make it easier to support other languages.
Writing the glue code is not rocket science, but it is a lot of work. An early post mentioned 38,000 lines of Python. There are a lot more now. Particularly since Python is used for major portions of the User Interface.
The Python UI is new complication for embedding another interpreter. At first glance, it suggests a need to integrate the current Python interpreter with the new one.
This isn't meant to be discouraging, but many software projects have grounded on the shoals of Too Much Work. Personally, I'd love to program Blender in Scheme. As fat old commie Mao Tse Tung said, "Let a thousand scripting languages bloom!"