clpython-devel

Download

clpython-devel@common-lisp.net

May 2007

2 participants
2 discussions

[clpython-devel] import fails due to null search paths in *habitat*
by Robert Dodier 05 May '07

05 May '07

Hello, I'm running CL-Python w/ Allegro Express 8.0 on Linux. I find that import fails for anything except stuff in the current working directory. That appears to be because *habitat* has search paths = nil. I tried (setf (habitat-search-paths *habitat*) <stuff>) and that works OK for importing .py files but attempting to import built-in stuff like sys fails. Is there some better way to establish the seach path? Shouldn't the built-in stuff be findable via the default seach paths? Thanks a lot for your help, Robert Dodier

2 3

[clpython-devel] calling Lisp from Python and vice versa
by Robert Dodier 05 May '07

05 May '07

Hello, I am interested in using CL-Python as a front end for Lisp libraries. To this end, I wonder how to call a Lisp function from withing Python. I know you can enter " (foo bar)" to call a Lisp function, but its return value is not known to Python. I'd like to be able to do something like "x = foo(bar)". Couple of questions related to this. How can I reference Lisp variables from Python and vice versa? Can I use import to load a Lisp file? After loading the Lisp file, how do functions and variables in it appear in Lisp --- does the Lisp package name come into play? What about Lisp symbols which contain characters not allowed in Python --- is there a way to escape them? Can a Lisp function return arbitrary Lisp objects, and if so how are those displayed in Python? Thanks a lot to Willem Broekma for inventing and maintaining CL-Python. I think it's a great idea. My immediate interest is to use CL-Python as an interface for the symbolic computation system Maxima which is written in CL. best, Robert Dodier

2 1