Preview: Burgled-Batteries, Yet Another Python-Lisp Bridge
(push :burgled-batteries.guess-not-grovel *features*) ; optional; avoids the groveller
(asdf:load-system "burgled-batteries")
(in-package #:burgled-batteries)
(run "1+1") ; ⇒ 2
(run "[1, 2, 3]") ; ⇒ #(1 2 3)
(run "(1, 2, 3)") ; ⇒ (1 2 3)
(run "dict(a=1, b=2, c=3)") ; ⇒ #
(alexandria:hash-table-alist *)
; ⇒ (("b" . 2) ("c" . 3) ("a" . 1))
(import "feedparser")
(defpyfun "feedparser.parse" (url))
(documentation 'feedparser.parse 'function)
; ⇒ "Parse a feed from a URL, file, stream, or string"
(feedparser.parse "http://pinterface.livejournal.com/data/atom")
; ⇒ #
(gethash "title" (first (gethash "entries" *)))
; ⇒ "Preview: Burgled-Batteries, Yet Another Python-Lisp Bridge"
To answer the most obvious question: CL-Python seems to require more resources than I can give it, Python-on-Lisp is incomplete and poorly integrated (also: I'll probably steal code from it), and pyffi is ... what I started from. If you count Python-on-Lisp-ex, this is the fifth Lisp/Python mashup I know about. Hopefully, it will be the last. ;)
Edit Oct. 11, 2011: Lots more to do yet, but if anybody is interested in throwing things at it, `darcs get http://repo.kepibu.org/burgled-batteries/`. Feel free to e-mail me directly, or ping the mailing list.
To answer the most obvious question: CL-Python seems to require more resources than I can give it, Python-on-Lisp is incomplete and poorly integrated (also: I'll probably steal code from it), and pyffi is ... what I started from. If you count Python-on-Lisp-ex, this is the fifth Lisp/Python mashup I know about. Hopefully, it will be the last. ;)
Edit Oct. 11, 2011: Lots more to do yet, but if anybody is interested in throwing things at it, `darcs get http://repo.kepibu.org/burgled-batteries/`. Feel free to e-mail me directly, or ping the mailing list.