Is D a good choice for embedding python/octave/julia

[Chris Wright via Digitalmars-d-learn]

On Sun, 13 Mar 2016 13:02:16 +0000, Bastien wrote:
> The sticking point is unless I commit the rest of my life to maintaining
> this software, I can't write it all in D. The algorithms change/are
> improved yearly; the output format from the instrument changes once in a
> while and therefore these need to be easily scripted/modified by other
> (non-programming) scientists and the community that only really know
> python and octave.

http://code.dlang.org/packages/pyd has you covered.

The degree to which it has you covered is based on how much you can wrap 
expensive operations up opaquely. If it turns out next year that someone 
has a new algorithm they need for something you implemented in D, it's 
going to be more work overall.