Until C-in-C works for all the features in Clojure (as long as it makes sense), clojure-py will have to wait since vanilla clojure already provides that.
0MQ seems interesting. The big advantage I see to this approach is it takes care of marking when a send is completed while the program is still running, so I don't have to re-incur the startup and shutdown overhead. importing sympy takes a lot of time so this might be worthwhile > Since you can't bring the python to the JVM you could try bringing the > clojure to python with clojure-py[1] :). Clojure-py is pretty new though > so depending on the nature of your project it may not be a great fit. > Another option for inter-process communication would be to use zeromq since > both python and clojure bindings exist. This would at least be a better > solution than shelling out to python everything time you needed to use the > library. > > -Ben > > > 1. https://github.com/halgari/clojure-py > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
