clpython-devel

clpython-devel@common-lisp.net

46 discussions

[clpython-devel] Running pybench with clpython
by Luís Oliveira 18 Aug '09

18 Aug '09

Hello, I'm trying to run pybench with clpython. It fails for me pretty early by not finding the 'platform' module. Has anyone tried to do this before? Thanks in advance, -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/

2 3

[clpython-devel] Build error
by Jason Nielsen 08 Aug '09

08 Aug '09

I've just git pulled the latest version of cl-python and am getting the following build error: <snip> ; compiling (YACC:DEFINE-PARSER *CL-YACC-PYTHON-PARSER* ...) ; compiling (DEFMETHOD LEXER-EOF-TOKEN ...) ; compiling (DEFMETHOD PARSE-FORM-WITH-YACC ...); compilation aborted because of fatal error: ; READ failure in COMPILE-FILE: ; SB-INT:SIMPLE-READER-PACKAGE-ERROR at 2660 (line 59, column 62) on #<SB-SYS:FD-STREAM for "file /home/jdn/work/lisp/cl-python/parser/grammar-clyacc.lisp" {1005DE4541}>: ; The symbol "YACC-EOF-SYMBOL" is not external in the YACC package. ; compilation aborted after 0:00:10.417 WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL {1003130FA1}> on #<CL-SOURCE-FILE "grammar-clyacc" {100351D501}>. unhandled ASDF:COMPILE-FAILED in thread #<SB-THREAD:THREAD "initial thread" RUNNING {10029DDD71}>: erred while invoking #<COMPILE-OP NIL {1003130FA1}> on #<CL-SOURCE-FILE "grammar-clyacc" {100351D501}> 0: (SB-DEBUG::MAP-BACKTRACE #<CLOSURE (LAMBDA #) {1003F3F679}>)[:EXTERNAL] 1: (BACKTRACE 128 #<SYNONYM-STREAM :SYMBOL SB-SYS:*STDERR* {1000172DD1}>) 2: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<ASDF:COMPILE-FAILED {1003E2B3C1}> #<unavailable argument>) 3: (INVOKE-DEBUGGER #<ASDF:COMPILE-FAILED {1003E2B3C1}>) 4: (ERROR ASDF:COMPILE-FAILED)[:EXTERNAL] 5: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) </snip> Cheers, Jason

2 3

[clpython-devel] Fwd: mixed Lisp/Python source code
by Willem Broekema 02 Aug '09

02 Aug '09

Hi everyone, I just posted the following on comp.lang.lisp; it's about a new feature (in development) to support mixed Lisp/Python syntax. Hope you find it interesting. http://groups.google.nl/group/comp.lang.lisp/browse_frm/thread/1861e201b6ea… (copied below; I've shortened the irrelevant long path names in the output) - Willem - - - On Aug 2, 9:10 pm, Oxide Scrubber <jharri...(a)hatlop.de> wrote: > vippstar wrote: > > With CL macros you can have any embedded language expanding to lisp > > code, but the embedded language can't have a language feature that CL > > does not, that's the only limitation. > Balderdash. Any language feature that can be implemented by a Turing > machine can be included, using a suitable macro to implement it. And don't forget reader macros: they gives you _complete_ control over syntax. Python and Ruby source code can be supported directly, with the right readtable. CLPython defines a readtable that dispatches every input character to the Python parser, and Python source files are then compiled using basically: (let ((*readtable* *python-parsing-readtable*)) (compile-file "source.py")) Even more interesting is a mixed-syntax Python/Lisp readtable. It's in development, here is a preview: clpython(213): (.parser::enter-mixed-lisp-python-syntax) ; The mixed Lisp/Python syntax mode is now enabled; Lispy *readtable* is now set. clpython(214): range(100)[98:2:-2] #(98 96 94 92 90 88 86 84 82 80 ...) clpython(215): import os #<module `os' :src #P"/System/Library/Frameworks/.../python2.5/os.py" :binary #P"/Users/willem/.fasl/.../2.5/lib/python2.5/os.fasl" :src-time 3400632679 :bin-time 3457618461 @ #x121964e2> clpython(216): os.urandom(1) "M" clpython(217): (funcall ~os.urandom 1) "¹" clpython(218): (format nil "OS is a ~A, and its source file is ~A" (type-of ~os) (module-src-pathname ~os)) "OS is a module, and its source file is /System/..../python2.5/os.py" Compiling and running a mixed-syntax file, using the normal compile- file and load functions: - - - foo.lispy - - - (in-package :cl-user) (clpython.parser::enter-mixed-lisp-python-syntax) def pyfact(x): if x <= 1: return 1 else: return x * lispfact(x-1) (defun lispfact (x) (if (<= x 1) 1 (* x (clpython:py-call ~pyfact (1- x))))) (trace lispfact) print pyfact(10) - - - clpython(203): :cf ;;; Compiling file foo.lispy ; The mixed Lisp/Python syntax mode is now enabled; Lispy *readtable* is now set. ;;; Writing fasl file foo.fasl ;;; Fasl write complete clpython(204): :ld ; Fast loading foo.fasl 0[2]: (lispfact 9) 1[2]: (lispfact 7) 2[2]: (lispfact 5) 3[2]: (lispfact 3) 4[2]: (lispfact 1) 4[2]: returned 1 3[2]: returned 6 2[2]: returned 120 1[2]: returned 5040 0[2]: returned 362880 3628800 > With the right set of macros you could probably give your embedded language > first-class continuations, for instance. Good guess... CLPython has a Python CPS convertor, to support generator expressions. > The macros will essentially compile it to CL the way GCC compiles C to assembly. Yeah, Common Lisp makes an excellent implementation language for Python, and probably Ruby too. It's almost cheating. - Willem

1 0

[clpython-devel] Cannot import
by Seo Sanghyeon 27 Jul '09

27 Jul '09

$ sbcl * (require 'clpython) * (clpython.app.repl:repl) >>> import sys >>> sys.path.append('/usr/lib/python2.5') >>> import types debugger invoked on a CLPYTHON.USER.BUILTIN.TYPE.EXCEPTION:|ImportError| in thread ImportError: Could not find module/package `types'.Search paths tried: ".", "/usr/lib/python2.5" Any idea? -- Seo Sanghyeon

2 5

[clpython-devel] Compile error
by Seo Sanghyeon 20 Jul '09

20 Jul '09

I cloned the reposity from GitHub. When I tried to compile it I get: ; compiling file "/home/tinuviel/github/cl-python/core/metaclass.lisp" ; compiling (IN-PACKAGE :CLPYTHON); compilation aborted because of fatal error: ; READ failure in COMPILE-FILE: ; SB-INT:SIMPLE-READER-PACKAGE-ERROR at 2925 (line 111, column 30) ; Symbol "DEFINE-HASH-TABLE-TEST" not found in the SB-INT package. I am using Debian Sid, and installed SBCL, closer-mop, ptester from the Debian repository. sbcl 1.0.29.11 cl-closer-mop 0.42 cl-ptester 1.2 -- Seo Sanghyeon

2 1

[clpython-devel] GitHub repo
by Willem Broekema 15 May '09

15 May '09

CLPython is now available on GitHub: http://github.com/franzinc/cl-python - Willem

1 0

[clpython-devel] News: moving to git, source-level debugging, Clozure support
by Willem Broekema 11 May '09

11 May '09

Hi all, some news from the CLPython front: 1. CLPython will very soon move to a git repository. This should make it much easier to contribute, hint hint! (More instructions to follow.) 2. At the International Lisp Conference in Cambridge, there was a tutorial by Duane Rettig (Franz Inc) and me. Duane showed source level debugging, a new feature in the upcoming Allegro 8.2, and I demonstrated a Python debugger/stepper built on top of the new Allegro functionality. The Python debugger is still very limited; hopefully it's stable and useful when Allegro 8.2 is released, whenever that is. 3. CLPython now runs on Clozure, too. - Willem

1 0

[clpython-devel] Build error
by Jason Nielsen 11 Feb '09

11 Feb '09

With a recent cvs checkout I get the follow error when building clpython: ; compiling (DEFGENERIC PY-** ...); compilation aborted because of fatal error: ; READ failure in COMPILE-FILE: ; SB-INT:SIMPLE-READER-PACKAGE-ERROR at 134051 (line 3470, column 49) on #<SB-SYS:FD-STREAM for "file /home/jdn/work/lisp/clpython/core/classes.lisp" {1003B44871}>: ; Symbol "__POW__" not found in the CLPYTHON.USER package. ; compilation aborted after 0:00:03 WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL {10029050F1}> on #<CL-SOURCE-FILE "classes" {1002AE4411}>. debugger invoked on a ASDF:COMPILE-FAILED in thread #<THREAD "initial thread" RUNNING {100266AA41}>: erred while invoking #<COMPILE-OP NIL {10029050F1}> on #<CL-SOURCE-FILE "classes" {1002AE4411}> I am on a Ubuntu 8.10 box running sbcl 1.0.18. With regards, Jason

2 1

[clpython-devel] CMUCL now also supported
by Willem Broekema 19 Jan '09

19 Jan '09

CLPython now also runs on CMUCL Snapshot 2009-01 (19E). This is in addition to the already supported implementations: Allegro CL, Lispworks and SBCL. Does anyone have a strong wish to have CLPython ported to yet another implementation? - Willem

2 4

[clpython-devel] Creating executables from Python functions (SBCL)
by Willem Broekema 17 Jan '09

17 Jan '09

It's now possible to create standalone executables from Python functions with SBCL (and only tested on Mac OS X). It is implemented on top of SBCL's function save-lisp-and-die. Using this functionality is straightforward: just call the method _exe() of the function. Example: * (clpython:repl) Welcome to CLPython, an implementation of Python in Common Lisp. Running on: SBCL 1.0.20 REPL shortcuts: `:q' = quit, `:h' = help. >>> def f(): print "hello world" ... #<function f> >>> f() hello world None >>> f._exe() Building executable will terminate the Lisp session. Continue? (y or n) y Writing SBCL repl executable to: clpython-sbcl-20090105-f [undoing binding stack and other enclosing state... done] [saving current Lisp image into /Users/willem/dev/lisp/tmp/test-python/python/clpython-sbcl-20090105-f: writing 2872 bytes from the read-only space at 0x04000000 writing 1616 bytes from the static space at 0x04100000 writing 29245440 bytes from the dynamic space at 0x10000000 done] [willem test-python]$ ls -l ./python/clpython-sbcl-20090105-f -rwxr-xr-x 1 willem willem 29462540 Jan 17 18:50 ./python/clpython-sbcl-20090105-f [willem test-python]$ ./python/clpython-sbcl-20090105-f hello world [willem test-python]$ The executables have access to the command line arguments via "sys.argv". That should make it straightforward to write small utility programs. Here is an example program that takes input from the command line. Type it all in the repl: import sys def fact(n): if n <= 1: return 1 else: return n * fact(n-1) def main(): # read argument from command line, using 10 as default if len(sys.argv) > 0: n = int(sys.argv[0]) else: n = 10 print "fact(%s):" % n print fact(n) main._exe() This gives an executable that behaves like this: [willem test-python]$ ./python/clpython-sbcl-20090105-main fact(10): 3628800 [willem test-python]$ ./python/clpython-sbcl-20090105-main 20 fact(20): 2432902008176640000 - Willem

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

clpython-devel