clpython-devel

clpython-devel@common-lisp.net

46 discussions

[clpython-devel] Fwd: Project silence and exposure
by Willem Broekema 17 Dec '06

17 Dec '06

Link to message: http://groups.google.com/group/comp.lang.python/msg/cd237cfa53c103e4 ---------- Forwarded message ---------- From: Willem Broekema <metawilm(a)gmail.com> Date: Dec 14, 2006 8:01 PM Subject: Re: CLPython (was Re: merits of Lisp vs Python) To: Paul Boddie wrote: > What would it take to get Python people more interested in it? I've > been monitoring the site [1] and the mailing list [2] for some time, > but nothing particularly visible seems to be happening. Well, judging from the reactions on blogs to the initial announcement here, quite some people have heard about it and seem interested. But that didn't result in more people hacking on it, which is unfortunate. I guess in part it's because there are not that many people really into both Python and Lisp, and those who are might not find this an interesting project because there is nothing "wow" to show, yet. So you are right about the project silence. Right now it's a one-person pet project, and progress is slow. But I'm already quite happy about the current state: stable, usable, and fairly complete. As for more exposure: I'd prefer to wait with big announcements until there are really interesting things achieved. Thanks a lot for your interest and comments! - Willem

1 0

[clpython-devel] Status update
by Willem Broekema 17 Dec '06

17 Dec '06

Dear clpython-devel members, It has been quiet on this mailing list for a long time. I'd like you to know that the project is stil alive, and that there is still progress, albeit slowly. On comp.lang.{lisp,python} there was a discussion about Python versus Lisp. CLPython was mentioned, and I wrote a bit about the current status and the future. I'll forward the three messages I wrote there, as it's about time you get an update, and so that people new to the project will find it in the list archive. Sorry for the duplication if you read the thread in the newsgroup already. If anything is unclear about how things currently work, or if you have suggestions for future directions, then please reply - that's what this list is for! :) Cheers, - Willem

1 0

[clpython-devel] coroutines
by paul cannon 10 Aug '06

10 Aug '06

This project is very interesting, and once it's working on sbcl I'd like to dig into it a bit more. Thanks for the good work. I saw some mention of coroutines in the list archive. I spent some time working on implementing some python-ness in lisp, and have a partially complete code transformer that can make generators and coroutines possible. It's sort of a state machine output; I don't know how it compares to the method mentioned by Ben used by c#. I could make it available if there is interest, and hopefully even complete it :) -- paul

2 1

[clpython-devel] public CVS available
by Willem Broekema 23 Jul '06

23 Jul '06

Hi everone, and thanks for your interest in CLPython. The source code is available in a public cvs server. To check out the code: export CVSROOT=:pserver:cvspublic@cvspublic.franz.com:/cvs-public login cvs co python - Wlilem

1 0

[clpython-devel] Re: clpython-devel Digest, Vol 1, Issue 1
by Ben 15 Jul '06

15 Jul '06

> Hi Ben, > > Congratulations for sending the first post to CLPython-devel :-) my interest in the project was to attempt to port the large number of interesting and high quality pure python libraries out there to lisp. seems like a worthwhile goal. i would have expected other lispers to realize there's a lot of low hanging fruit out there. > It's the easy approach, and it more or less proves that Python as > language is a subset of Common Lisp. Well, except for generators, as > CL does not have a 'yield'-like operations. presumably this can be simulated either with CPS or a state machine (that's how C# does it, at least.) > Right now all the b*.py benchmark files can be run successfully on that's fantastic! > I had listed the two most important dependencies (in my eyes) on > Allegro CL at the moment. I know about the existence of CL-Yacc; never > used it, though I assume it should not be too much work to let > CLPython play nicely with it. > > As for the environments, I'd have to look more into that. Allegro CL > has extended the CLTL2 environments, and I use ACL's functionality. > > If it's possible to use custom declaration types (declare (pydecl > ...)); and if it's possible to get the value of those declarations > from an &environment variable in macros, that might be enough already > for what the Python compiler needs. it looks like the environment support in sbcl is somewhat rudimentary. in particular, there is no define-declaration. i don't know if it would be difficult to add. however, franz has generously supplied a portable environments implementation http://lispwire.com/entry-proganal-envaccess-des which they claim works on sbcl. it is LLGPL. > You mention creating a compatiblity layer. Perhaps ACL-compat offers a > lot of the desired functionality already? that's an idea. another idea is to use the various proto-standards that are floating around for things like network, fs, et cetera. > Good to see you're interested :-) unfortunately i'm supposed to be finishing a dissertation soon. so i don't have time myself in the short term. but eventually i will have time and hope to be able to help. keep us informed! regards, B

1 0

[clpython-devel] plans (and porting)
by Ben 14 Jul '06

14 Jul '06

hi -- fantastic work. i actually had tried in my spare time to do something like this, but using a hack where i used the AST python module to do the parsing. browsing the source, i see python functions -> lisp functions, python (meta)classes -> CLOS (meta)classes, etc. this is great! what are your plans? have you tested it on any big python modules? i wanted to know what your thoughts were on porting to another lisp. i'd like to try to port to SBCL, which supports cltl2 environments, and i think there are some free yacc-like packages out there (none of which i've used, though.) in general imagine an implementation-specific compatibility layer will be needed, to bootstrap most python modules (regexps, network, etc.) great work! Ben

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

clpython-devel