| description | repo for burgled-feedparser |
| last change | Sat, 24 Dec 2011 22:55:44 |
| url | http://repo.kepibu.org/burgled-feedparser/ |
| project url | http://code.kepibu.org/burgled-feedparser/ |
| mailing list url | http://lists.kepibu.org/listinfo/burgled-feedparser |
| 24 Dec 2011 22:55 | pinterface | Forgot dependencies | commit | commitdiff |
| 24 Dec 2011 22:41 | pinterface | Eh, I guess org-mode prefers code blocks indented | commit | commitdiff |
| 24 Dec 2011 22:40 | pinterface | Get rid of the hash-reader stuff; ACCESS is better | commit | commitdiff |
| 24 Dec 2011 22:39 | pinterface | Initial import | commit | commitdiff |
burgled-feedparser: Python’s Universal Feed Parser, from Common Lisp
burgled-feedparser provides a Common Lisp interface to Python’s Universal Feed Parser using the burgled-batteries library.
(asdf:load-system "burgled-feedparser") (burgled-feedparser:parse "http://pinterface.livejournal.com/data/atom") ; => #<HASH-TABLE>
I like Common Lisp better than Python. Python, on the other hand, has the defacto library for parsing feeds. Rather than tackle the immense job of attempting to port it and any dependencies which don’t current exist in CL; or writing some code in Python which outputs into a specific format that then must be parsed on the Lisp side; it seemed best to simply integrate the Python library into the CL image itself.
Basically, why port what you can subsume?
burgled-feedparser has four exported symbols.
feedparser.parse(). This translates CPython pointers into Lisp objects as per BURGLED-BATTERIES.feedparser.USER_AGENT.