- clpython-devel@common-lisp.net - mailman3.common-lisp.net

[clpython-devel] `#1=(,) ... `#1# fails on ccl.
by Pascal J. Bourguignon 16 Jan '13

16 Jan '13

Hi! When trying to load a module (import ast) in clpython on ccl (1.9-dev-r15508), it fails on `(let* ((.undecorated-func #1#) ...) with the following patch, it works better. Since the expansion of #\` is implementation dependent, it might be safer to avoid kludges involving it. ------------------------------------------------------------------------------------------------------ diff --git a/compiler/compiler.lisp b/compiler/compiler.lisp index 6bbc61a..adf8bb7 100644 --- a/compiler/compiler.lisp +++ b/compiler/compiler.lisp @@ -1212,15 +1212,19 @@ LOCALS shares share tail structure with input arg locals." (if **-arg #x08 0) (if generator-p #x20 0))))) (when (keywordp fname) - (return-from funcdef-stmt-1 `#1=(make-py-function :name ',fname - :context-name ',context-fname - :lambda ,func-lambda - :func-globals ,(get-module-namespace e) - :func-code ,func-code))) + (return-from funcdef-stmt-1 `(make-py-function :name ',fname + :context-name ',context-fname + :lambda ,func-lambda + :func-globals ,(get-module-namespace e) + :func-code ,func-code))) (let ((art-deco '.undecorated-func)) (dolist (x (reverse decorators)) (setf art-deco `(py-call ,x ,art-deco))) - `(let* ((.undecorated-func #1#) + `(let* ((.undecorated-func (make-py-function :name ',fname + :context-name ',context-fname + :lambda ,func-lambda + :func-globals ,(get-module-namespace e) + :func-code ,func-code)) (.decorated-func ,art-deco)) ;; Ugly special case: ;; class C: ------------------------------------------------------------------------------------------------------ -- __Pascal Bourguignon__

2 1

Re: [clpython-devel] No such symbol in pkg clpython: py-<
by Pascal J. Bourguignon 12 Jan '13

12 Jan '13

Hi! Trying clpython from quick lisp, it fails with the following error. Obviously, somebody forgot with-standard-io-syntax between format and intern... ; SLIME 2012-09-04 cl-user> (ql:quickload :clpython) To load "clpython": Load 1 ASDF system: clpython ; Loading "clpython" ;;; Compiling Python grammar for CL-Yacc... .................................................. [package clpython.lispy.stuff].................... [package clpython.module.array]................... [package clpython.module.binascii]................ [package clpython.module.cstringio]............... [package clpython.module.errno]................... [package clpython.module.exceptions].............. [package clpython.module.gc]...................... [package clpython.module.imp]..................... [package clpython.module.math].................... [package clpython.module.operator]................ [package clpython.module.posix]................... [package clpython.module._random]................. [package clpython.module.re]...................... [package clpython.module._socket]................. [package clpython.module.string].................. [package clpython.module.symbol].................. [package clpython.module.sys]..................... [package clpython.module.thread].................. [package clpython.module.time]...1 No such symbol in pkg clpython: py-< [Condition of type simple-condition] Restarts: 0: [continue] Return from BREAK. 1: [retry-compile-file] Retry compiling #P"/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp/software/clpython-20110730-git/lib/operator.lisp" 2: [skip-compile-file] Skip compiling #P"/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp/software/clpython-20110730-git/lib/operator.lisp" 3: [retry] Retry compiling #<cl-source-file "clpython.lib" "lib" "operator">. 4: [accept] Continue, treating compiling #<cl-source-file "clpython.lib" "lib" "operator"> as having been successful. 5: [abort] Give up on "clpython" --more-- Backtrace: 0: (clpython.module.operator::sym->op #<Unknown Arguments>) 1: (#<Anonymous Function #x3020032FA5AF>) 2: (ccl::cheap-eval-in-environment (list* 'progn (loop clpython.module.operator::for (clpython.module.operator::m.. 3: (ccl::cheap-eval (list* 'progn (loop clpython.module.operator::for (clpython.module.operator::meth clpython.mo.. 4: (ccl::read-dispatch #<basic-file-character-input-stream ("/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp.. 5: (ccl::%parse-expression #<basic-file-character-input-stream ("/Volumes/Data/pbourguignon/quicklisp/dists/quick.. 6: (ccl::%read-form #<basic-file-character-input-stream ("/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp/so.. 7: (ccl::read-internal #<basic-file-character-input-stream ("/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp.. 8: (ccl::read-recording-source #<basic-file-character-input-stream ("/Volumes/Data/pbourguignon/quicklisp/dists/q.. 9: (ccl::fcomp-read-loop "/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp/software/clpython-20110730-git/lib.. 10: (ccl::fcomp-file "/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp/software/clpython-20110730-git/lib/oper.. 11: (ccl::%compile-file "/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp/software/clpython-20110730-git/lib/o.. 12: (compile-file #P"/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp/software/clpython-20110730-git/lib/opera.. 13: (asdf:compile-file* #P"/Volumes/Data/pbourguignon/quicklisp/dists/quicklisp/software/clpython-20110730-git/lib.. 14: ((:internal (asdf:perform (asdf:compile-op asdf:cl-source-file)))) 15: (#<standard-method asdf::call-with-around-compile-hook (asdf:component t)> #<cl-source-file "clpython.lib" "li.. 16: (#<standard-method asdf:perform (asdf:compile-op asdf:cl-source-file)> #<compile-op (:verbose nil) #x3020025F8.. 17: (ccl::%%before-and-after-combined-method-dcode (nil #<standard-method asdf:perform (asdf:compile-op asdf:cl-so.. 18: (ccl::%%standard-combined-method-dcode ((#<standard-method asdf:perform :before (asdf:compile-op asdf:source-f.. 19: (nil #<Unknown Arguments>) 20: (nil #<Unknown Arguments>) 21: (#<standard-method asdf::perform-with-restarts (t t)> #<compile-op (:verbose nil) #x3020025F8C5D> #<cl-source-.. 22: (ccl::%call-next-method (nil #<standard-method asdf::perform-with-restarts (t t)> . 76455387)) 23: (#<standard-method asdf::perform-with-restarts :around (t t)> #<compile-op (:verbose nil) #x3020025F8C5D> #<cl.. 24: (ccl::%%standard-combined-method-dcode (#<standard-method asdf::perform-with-restarts :around (t t)> #<standar.. 25: (nil #<Unknown Arguments>) 26: ((:internal ccl::with-compilation-unit-body (asdf::perform-plan (list)))) 27: (ccl::call-with-compilation-unit #<ccl:compiled-lexical-closure (:internal ccl::with-compilation-unit-body (as.. 28: (#<standard-method asdf::perform-plan (list)> ((#1=#<load-op (:verbose nil) #x3020025EF12D> . #<cl-source-file.. 29: (ccl::%%check-keywords #(1 #() #<ccl:method-function asdf::perform-plan (list)>) 76455429) 30: (nil #<Unknown Arguments>) 31: ((:internal (asdf:operate (t t)))) 32: (asdf::call-with-system-definitions #<ccl:compiled-lexical-closure (:internal (asdf:operate (t t))) #x3020025D.. 33: (#<standard-method asdf:operate (t t)> asdf:load-op "clpython" :verbose nil) 34: (ccl::%%standard-combined-method-dcode ((#<standard-method asdf:operate :before (t t)>) nil #<standard-method .. 35: (nil #<Unknown Arguments>) 36: (asdf:oos asdf:load-op "clpython" :verbose nil) 37: ((:internal quicklisp-client::apply-load-strategy)) 38: (quicklisp-client::call-with-macroexpand-progress #<ccl:compiled-lexical-closure (:internal quicklisp-client::.. 39: (quicklisp-client::apply-load-strategy #<load-strategy "clpython" (1 asdf, 0 quicklisp)>) --more-- -- __Pascal Bourguignon__ http://www.informatimago.com

2 1

[clpython-devel] Habitats don't hold variable bindings?
by Scott L. Burson 25 Oct '11

25 Oct '11

Hi, I am just starting out with CLPython. I tried the example in section 2.4 of the manual, but it didn't work. (I tried both Clozure 1.6 and Allegro 8.1.) Even looking through the code, I can't find any evidence that variable bindings are stored in habitats. Am I missing something? -- Scott

2 1

[clpython-devel] import gives UnexpectedEofError
by Breanndán Ó Nualláin 22 Jun '11

22 Jun '11

I'm running into an error while trying to get CLPython up and running. The test suite fails on the first Python import test with an UnexpectedEofError. Any other attempt at importing gives the same error. For example these three lines of code give the error as below: (ql:quickload "clpython") (push #p"clpython-20110219-git/test/data" *CLPYTHON-MODULE-SEARCH-PATHS*) (clpython:run "import bar") ;; Parsing #P"clpython-20110219-git/test/data/bar.py" into #P"clpython-20110219-git/test/data/bar.py.lisp" ;; Error occured while reading input with the Python readtable: ;; UnexpectedEofError: Unexpected end of file. ;; Standard IO syntax (*readtable* etc) has been activated to enable debugging. debugger invoked on a CLPYTHON.USER.BUILTIN.TYPE.EXCEPTION:|UnexpectedEofError| in thread #<THREAD "initial thread" RUNNING {10029994E1}>: UnexpectedEofError: Unexpected end of file. It's the most recent quicklisp version of CLPython on Linux. SBCL 1.0.49 quicklisp version 2011051901 clpython-20110219-git Python 2.7.2 Linux 2.6.39

2 2

[clpython-devel] Problem with Python 'open'
by Mark McWiggins 25 May '11

25 May '11

Hi -- I have CLPython running on a small example with no I/O, but when I try opening a file I get: > Error: Incorrect keyword arguments in (NIL "r") . > While executing: OPEN, in process listener(1). > Type :POP to abort, :R for a list of available restarts. > Type :? for other options. for open(f,'r') or similar error: > Error: Incorrect keyword arguments in (NIL NIL) . > While executing: OPEN, in process listener(1). > Type :POP to abort, :R for a list of available restarts. > Type :? for other options. for open(f) Suggestions please! I'm not much of a Lisp hacker, just trying to get a Python script to run (much) faster. Thanks. -- Mark McWiggins 425-369-8286 (cell)

2 1

[clpython-devel] strange behaviour of python and mixed interpreters
by Nitralime 14 Apr '11

14 Apr '11

/*Hi folks!*/ I have installed clpython recently and encountered some problems while playing around with the provided interpreter modes. Here is a sample SLIME session -------------------------------------------------------------------------------- ; SLIME 2011-01-28 *CL-USER> (ql:quickload :clpython)* To load "clpython": Load 1 ASDF system: clpython ; Loading "clpython" ......... CLPython quick start guide: Run a string of Python code: (CLPYTHON:RUN "for i in range(4): print i") Run a Python file: (CLPYTHON:RUN #p"~/example/foo.py") Start the Python "interpreter" (REPL): (CLPYTHON.APP.REPL:REPL) To start mixed Python/Lisp input mode: (CLPYTHON.PARSER:ENTER-MIXED-LISP-PYTHON-SYNTAX) Run the test suite: (ASDF:OPERATE 'ASDF:TEST-OP :CLPYTHON) (:CLPYTHON) *CL-USER> (CLPYTHON.PARSER:ENTER-MIXED-LISP-PYTHON-SYNTAX)* ;; The mixed Lisp/Python syntax mode is now active: custom *readtable* is set. ;; Python variables will be interned in the #<PACKAGE "COMMON-LISP-USER">. ;; To exit the mixed mode: (CLPYTHON.PARSER:EXIT-MIXED-LISP-PYTHON-SYNTAX) ; No value *CL-USER> (+ 2 3)* -------------------------------------------------------------------------------- At this point the SLIME doesn't return back! I tested it also using a python expression. The same behaviour! C-c C-c drops the session into dubugger which in turn is not responsive! To terminate it the whole process must be killed. Tab completion also leads to a hanging emacs! ############################################################################### In a linux console it behaves differently but not exactly as described in the documentation. Here is a sample session: -------------------------------------------------------------------------------- *$ rlwrap sbcl* This is SBCL 1.0.47, an implementation of ANSI Common Lisp. More information about SBCL is available at <http://www.sbcl.org/>. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. ** (ql:quickload :clpython)* To load "clpython": Load 1 ASDF system: clpython ; Loading "clpython" ......... CLPython quick start guide: Run a string of Python code: (CLPYTHON:RUN "for i in range(4): print i") Run a Python file: (CLPYTHON:RUN #p"~/example/foo.py") Start the Python "interpreter" (REPL): (CLPYTHON.APP.REPL:REPL) To start mixed Python/Lisp input mode: (CLPYTHON.PARSER:ENTER-MIXED-LISP-PYTHON-SYNTAX) Run the test suite: (ASDF:OPERATE 'ASDF:TEST-OP :CLPYTHON) (:CLPYTHON) ** (CLPYTHON.PARSER:ENTER-MIXED-LISP-PYTHON-SYNTAX)* ;; The mixed Lisp/Python syntax mode is now active: custom *readtable* is set. ;; Python variables will be interned in the #<PACKAGE "COMMON-LISP-USER">. ;; To exit the mixed mode: (CLPYTHON.PARSER:EXIT-MIXED-LISP-PYTHON-SYNTAX) * (+ 2 3) 5 ** def double (n):* *return 2*n* #<CLOSURE (FLET CLPYTHON::|__main__.__main__/double|) {1002F8D129}> ** double (4)* 8 ** (double 4)* ; in: DOUBLE 4 ; (DOUBLE 4) ; ; caught STYLE-WARNING: ; undefined function: DOUBLE ; ; compilation unit finished ; Undefined function: ; DOUBLE ; caught 1 STYLE-WARNING condition debugger invoked on a UNDEFINED-FUNCTION in thread #<THREAD "initial thread" RUNNING {1002980D01}>: The function SB-ALIEN:DOUBLE is undefined. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. (SB-KERNEL::UNDEFINED-FUN-ERROR-HANDLER #<unavailable argument> #.(SB-SYS:INT-SAP #X7FFFF69F7480) #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X7FFFF69F7000 :TYPE (* (STRUCT SB-VM::OS-CONTEXT-T-STRUCT))> (21)) 0] 0 * -------------------------------------------------------------------------------- The evaluation of "(double 4)" fails. ################################################################################ There is also a problem with python repl: ; SLIME 2011-01-28 *CL-USER> (ql:quickload :clpython)* To load "clpython": Load 1 ASDF system: clpython ; Loading "clpython" ......... CLPython quick start guide: Run a string of Python code: (CLPYTHON:RUN "for i in range(4): print i") Run a Python file: (CLPYTHON:RUN #p"~/example/foo.py") Start the Python "interpreter" (REPL): (CLPYTHON.APP.REPL:REPL) To start mixed Python/Lisp input mode: (CLPYTHON.PARSER:ENTER-MIXED-LISP-PYTHON-SYNTAX) Run the test suite: (ASDF:OPERATE 'ASDF:TEST-OP :CLPYTHON) (:CLPYTHON) *CL-USER> (push "/usr/lib/python2.7" *clpython-module-search-paths*)* ("/usr/lib/python2.7") *CL-USER> (clpython:repl)* Welcome to CLPython, an implementation of Python in Common Lisp. Running on: SBCL 1.0.47 REPL shortcuts: `:q' = quit, `:h' = help. Using 1 default module search paths set in *CLPYTHON-MODULE-SEARCH-PATHS* *>>> import os* ;; Parsing #P"/usr/lib/python2.7/os.py" into #P"/usr/lib/python2.7/os.py.lisp" ;; Error occured while reading input with the Python readtable: ;; UnexpectedEofError: Unexpected end of file (line 752). ;; Standard IO syntax (*readtable* etc) has been activated to enable debugging. --- Debugger window ---------------------------------- UnexpectedEofError: Unexpected end of file (line 752). [Condition of type CLPYTHON.USER.BUILTIN.TYPE.EXCEPTION:|UnexpectedEofError|] Restarts: 0: [RETRY] Retry evaluating this top-level form in module `__main__' 1: [ERROR] Skip this top-level form in module `__main__' 2: [RETRY-REPL-EVAL] Retry the expression: "import os" 3: [RETURN-PYTHON-TOPLEVEL] Return to Python top level 4: [RETRY] Retry SLIME REPL evaluation request. 5: [*ABORT] Return to SLIME's top level. --more-- Just for testing purpose I have commented the following code block in os.py ----------------------------------------------- /..... 742 if not _exists("urandom"): 743 def urandom(n): 744 """urandom(n) -> str 745 746 Return a string of n random bytes suitable for cryptographic use. 747 748 """ 749 try: 750 _urandomfd = open("/dev/urandom", O_RDONLY) 751 except (OSError, IOError): 752 raise NotImplementedError("/dev/urandom (or equivalent) not found") 753 try: 754 bs = b"" 755 while n > len(bs): 756 bs += read(_urandomfd, n - len(bs)) 757 finally: 758 close(_urandomfd) 759 return bs/ ------------------------------------------------- and tried the "import os" again and got the same error: --- Debugger window ---------------------------------- UnexpectedEofError: Unexpected end of file. [Condition of type CLPYTHON.USER.BUILTIN.TYPE.EXCEPTION:|UnexpectedEofError|] Restarts: 0: [RETRY] Retry evaluating this top-level form in module `__main__' 1: [ERROR] Skip this top-level form in module `__main__' 2: [RETRY-REPL-EVAL] Retry the expression: "import os" 3: [RETURN-PYTHON-TOPLEVEL] Return to Python top level 4: [RETRY] Retry SLIME REPL evaluation request. 5: [*ABORT] Return to SLIME's top level. --more-- The situation under Clozure is even worse! The mixed interpreter doesn't work neither in SLIME nor directly in linux console.The python repl behaviour is similar to that of SBCL. I'm using Clozure 1.6-r14468M and SBCL 1.0.47 on Linux 64bit. The installed version of clpython ist "clpython-20110219-git". Are these known issues or am I missing something here? Any feedback is very much appreciated! Regards Nik

3 2

[clpython-devel] Python extension modules
by Nitralime 10 Apr '11

10 Apr '11

Hi! Can the Python (C-)extension modules be used in clpython? Which Python version does clpython implement? Regards Nik

1 0

[clpython-devel] ecl build
by David Dreisigmeyer 11 Feb '11

11 Feb '11

Hi, I was wondering if it's possible to install cl-python using ECL? I'm getting the error below using ecl 10.7.1. Thanks, -Dave > (ql:quickload "clpython") To load "clpython": Load 2 ASDF systems: closer-mop yacc Install 1 Quicklisp release: clpython ; Fetching #<url "http://beta.quicklisp.org/archive/clpython/2010-11-07/clpython-20101107-git…"> ; 217.01KB ================================================== 222,218 bytes in 0.13 seconds (1669.31KB/sec) ; Loading "clpython" .................................................. [package clpython.ast.reserved]................... [package clpython.ast.operator]................... [package clpython.ast.punctuation]................ [package clpython.ast.token]...................... [package clpython.ast.node]....................... [package clpython.ast.node-p]..................... [package clpython.ast]............................ [package clpython.user.builtin.function].......... [package clpython.user.builtin.type.exception].... [package clpython.user.builtin.type].............. [package clpython.user.builtin.value]............. [package clpython.user.builtin]................... [package clpython.user]........................... [package clpython.util]........................... [package clpython.parser]......................... [package clpython.module]......................... [package clpython]................................ [package clpython.app.repl] ;;; Note: ;;; Refusing to propagate #<form RPLACD 101dca120> ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/ASDF-TMP-package.c -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/ASDF-TMP-package.o ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinit7fFOd3.c -o /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinit7fFOd3.o ;;; Note: ;;; Invoking external command: ;;; gcc -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/package.fas -L/usr/local/lib/ /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinit7fFOd3.o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/package.o -bundle -lffi -lecl -lm ;;; Note: ;;; in file utils.lisp, position 2992 ;;; at (DEFGENERIC SLURP-FILE ...) ;;; Unknown type C::SEQUENCE-INDEXX. Assuming it is T.. ;;; Note: ;;; Refusing to propagate #<form WITH-STACK 101979090> ;;; Note: ;;; Refusing to propagate #<form RPLACD 1019fd630> ;;; Note: ;;; Refusing to propagate #<form RPLACD 101ae70f0> ;;; Note: ;;; Constant value optimized away or not used ;;; (\ /) ;;; Note: ;;; Constant value optimized away or not used ;;; (/) ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/ASDF-TMP-utils.c -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/ASDF-TMP-utils.o ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitegsHTs.c -o /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitegsHTs.o ;;; Note: ;;; Invoking external command: ;;; gcc -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/utils.fas -L/usr/local/lib/ /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitegsHTs.o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/utils.o -bundle -lffi -lecl -lm ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/ASDF-TMP-readtable.c -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/ASDF-TMP-readtable.o ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitGO8PW8.c -o /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitGO8PW8.o ;;; Note: ;;; Invoking external command: ;;; gcc -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/readtable.fas -L/usr/local/lib/ /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitGO8PW8.o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/readtable.o -bundle -lffi -lecl -lm ;;; Note: ;;; Refusing to propagate #<form RPLACD 102ae4090> ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/ASDF-TMP-macro-state.c -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/ASDF-TMP-macro-state.o ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinite5PGo3.c -o /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinite5PGo3.o ;;; Note: ;;; Invoking external command: ;;; gcc -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/macro-state.fas -L/usr/local/lib/ /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinite5PGo3.o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/macro-state.o -bundle -lffi -lecl -lm . ;;; Note: ;;; Refusing to propagate #<form RPLACD 102d1a060> ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/ASDF-TMP-patternmatch.c -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/ASDF-TMP-patternmatch.o ;;; Note: ;;; Invoking external command: ;;; gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -g -O2 -fPIC -fno-common -Ddarwin -O2 -w -c /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitPw8bop.c -o /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitPw8bop.o ;;; Note: ;;; Invoking external command: ;;; gcc -o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/patternmatch.fas -L/usr/local/lib/ /private/var/folders/SI/SIz9lIlTFcGEDtVWoSa4V++++TI/-Tmp-/eclinitPw8bop.o .cache/common-lisp/ecl-10.7.1-482368e2-macosx-x86/Users/daviddreisigmeyer/quicklisp/dists/quicklisp/software/clpython-20101107-git/util/patternmatch.o -bundle -lffi -lecl -lm (1 :AND :ALLEGRO :ALLEGRO-VERSION>= (:VERSION>= 8 2)) is not a valid feature expression.

2 4

[clpython-devel] c api?
by Seth Burleigh 24 May '10

24 May '10

I was wondering about the difficulties involved in adding the python c api, since it would be extremely useful.

2 4

[clpython-devel] Fwd: Moratorium on Python language changes
by Willem Broekema 22 Oct '09

22 Oct '09

Now that Python as language is fairly mature, at the point of getting features that don't add much value, Guido announced a moratorium on language changes for a few years, for both the 2.x and 3.x branches. This allows other implementations like us to catch up, which I appreciate. http://mail.python.org/pipermail/python-ideas/2009-October/006305.html - Willem

1 0

[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

[clpython-devel] Can not login to cvspublic.franz.com
by Al Bat 15 Jan '09

15 Jan '09

Hi ! Sorry for asking such a stupid question. Is there any other way to download the current snapshot of CLPython? I've tried *"cvs -d :pserver:cvspublic@cvspublic.franz.com:/cvs-public login"* with password "* cvspublic*", as it was recommended. However, as a result, I receive only*"Connection refused" *from the server. I'm not sure, whether the failure is at the server's side. Can anybody confirm that this *cvs* way works. And in the case if it doesn't, can anybody be so kind to give me a hint on any alternative way of getting CLPython. By the way, how big is it? Maybe, it can be sent via email? Thanks! Al

2 3

[clpython-devel] Calling Python functions from Lisp [Re Franz thread: spr35431]
by Stuart C. Shapiro 09 Jan '09

09 Jan '09

I think that I have successfully installed CLPython. What I want to do is to call Python functions, defined in programs written by others, from Allegro Common Lisp. So here is a test Python program called test.py: ----------------------------- # A Python file to use to test clpython def test(): print "I am a Python function." return "I am done." print("The Python test file has been run.") ----------------------------- I loaded clpython, and did (note: this wasn't the first time I imported test, so test.fasl and test.pyc already existed.): ----------------------------- cl-user(3): (clpython:run "import test; test.test()") Warning: *import-recompiled-files* = #<equal hash-table with 0 entries> Warning: /net/projects/shapiro/clpython/test.fasl not in #<equal hash-table with 0 entries> ; Fast loading /net/projects/shapiro/clpython/test.fasl The Python test file has been run. Warning: *import-recompiled-files* = #<equal hash-table with 0 entries> Warning: /net/projects/shapiro/clpython/test.fasl not in #<equal hash-table with 0 entries> I am a Python function. "I am done." ----------------------------- First question: Why the Warning messages? How can I get rid of them? Notice that I can make use of the values returned by the Python function: ----------------------------- cl-user(4): (setf x (clpython:run "import test; test.test()")) Warning: *import-recompiled-files* = #<equal hash-table with 0 entries> Warning: /net/projects/shapiro/clpython/test.fasl not in #<equal hash-table with 0 entries> ; Fast loading /net/projects/shapiro/clpython/test.fasl The Python test file has been run. Warning: *import-recompiled-files* = #<equal hash-table with 0 entries> Warning: /net/projects/shapiro/clpython/test.fasl not in #<equal hash-table with 0 entries> I am a Python function. "I am done." cl-user(5): x "I am done." ----------------------------- What I'd really like to do now is to call test.test() as much as possible as though it were a Common Lisp function. One possible way is: ----------------------------- cl-user(6): (clpython:run "test.test()") Error: NameError: Variable `test' is unbound. [condition type: NameError] Restart actions (select using :continue): 0: Enter a Lisp value to use for `test'. 1: Return to Top Level (an "abort" restart). 2: Abort entirely from this (lisp) process. ----------------------------- But, the name of the function does not seem to survive from one call of clpython:run to another. Final question: How can I do this? stu -- Stuart C. Shapiro Professor, Department of Computer Science and Engineering University at Buffalo, The State University of New York 201 Bell Hall, Box 602000, Buffalo, NY 14260-2000, U.S.A. PHONE: 716-645-3180x125 FAX: 716-645-3464 shapiro(a)cse.buffalo.edu http://www.cse.buffalo.edu/~shapiro/

2 4

[clpython-devel] Will CLPython have a GIL?
by Anand Patil 03 Oct '08

03 Oct '08

Hi everyone, Will CLPython have a global interpreter lock? Will it allow different threads to touch Python objects simultaneously on different cores? Thanks, Anand

2 3

[clpython-devel] Installation problems
by Anand Patil 24 Sep '08

24 Sep '08

Hello, I'm trying to follow the installation instructions at http://common-lisp.net/project/clpython/ but it doesn't seem to be working. I know absolutely nothing about Lisp, so some more detailed step-by-step instructions would be very helpful. Here's what happens: * (require 'asdf) ("ASDF") * (asdf:operate 'asdf:load-op :clpython) ; loading system definition from /Users/anand/clpython.asd into ; #<PACKAGE "ASDF0"> ; registering #<SYSTEM :CLPYTHON.PACKAGE {11A97AD9}> as CLPYTHON.PACKAGE ; registering #<SYSTEM :CLPYTHON.DEPEND {11CB5CE1}> as CLPYTHON.DEPEND ; registering #<SYSTEM :CLPYTHON.PARSER {11E49B21}> as CLPYTHON.PARSER ; registering #<SYSTEM :CLPYTHON.CORE {11FE6E79}> as CLPYTHON.CORE ; registering #<SYSTEM :CLPYTHON.LIB {1217F4F1}> as CLPYTHON.LIB ; registering #<SYSTEM :CLPYTHON.APP.REPL {11719139}> as CLPYTHON.APP.REPL ; registering #<SYSTEM :CLPYTHON.APP.PROFILER {118C4F59}> as ; CLPYTHON.APP.PROFILER ; registering #<SYSTEM :CLPYTHON.APP {11A6FEA1}> as CLPYTHON.APP ; registering #<SYSTEM :CLPYTHON {11C05761}> as CLPYTHON debugger invoked on a ASDF:MISSING-DEPENDENCY: component :CLOSER-MOP not found, required by #<SYSTEM "clpython.core" {122B0A71}> Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [ABORT] Exit debugger, returning to top level. ((LABELS ASDF::DO-ONE-DEP) ASDF:COMPILE-OP :CLOSER-MOP NIL) 0] Thanks in advance, Anand

2 1

[clpython-devel] Re: CLPython on SBCL
by Jason Nielsen 07 Jul '08

07 Jul '08

I can confirm that compilation fails using SBCL 1.0.16 on a Ubuntu 7.10 system with a: "has no suitable method for STREAM-ELEMENT-TYPE, and so has fallen through to this method...." error that crashes the whole session. You can reproduce this behaviour with the following: (defclass foo (standard-class) ()) (defclass bar () () (:metaclass foo)) Cheers, Jason

3 23

[clpython-devel] New errors in recent CVS
by Jason Nielsen 14 Jun '08

14 Jun '08

Hello, I just pulled the recent changes from cvs and get the following warning when building: The constant CLPYTHON.PARSER::+ALL-VALUES-NAMES+ is being redefined (from (CLPYTHON.PARSER:+NORMAL-VALUE+ CLPYTHON.PARSER:+AUGASSIGN-VALUE+ CLPYTHON.PARSER:+NO-VALUE+) to (CLPYTHON.PARSER:+NORMAL-VALUE+ CLPYTHON.PARSER:+AUGASSIGN-VALUE+ CLPYTHON.PARSER:+NO-VALUE+)) which I accept and the build finishes. When I run the test suite I get the following: ********************************** End CLPython test Errors detected in this test: 104 UNEXPECTED: 100 Successes this test:609 ; ; compilation unit finished ; caught 114 fatal ERROR conditions ; caught 4 ERROR conditions ; caught 3 WARNING conditions ; caught 22 STYLE-WARNING conditions ; printed 26 notes NIL There are a whole bunch of error messages when running the tests of the form: Reason: detected an unexpected error of type `#<SB-PCL::CONDITION-CLASS SB-C:COMPILER-ERROR>': which are the likely cause of the 100 extra failures. All of this is on a Ubuntu 7.10 box with sbcl 1.0.17... I built the latest sbcl along with the previous tarball I had and the test suite ran as expected so the problem is in recent updates. By the way I've been following Euro 2008 closely (I'm a huge soccer/football fan which isn't quite as common here in Canada) and the Dutch team are looking awesome! Nothing like kicking the asses of the reigning world champs and runners-up to start off the tournament ;-). Jason

2 2

[clpython-devel] Python just got a bit less dynamic
by Willem Broekema 13 Jun '08

13 Jun '08

Guido just limited the dynamicness of Python in a very sensible way, by declaring that the attributes of objects can only be regular strings. For users this does not change much, but for implementors this has significant benefits, so I like this limitation a lot. The implementation of attributes in CLPython and other implementations can now be cleaned up and made more efficient by removing hairy corner cases. CLPython can now always represent attributes by Lisp symbols. Also as a result, the five known failures in the CLPython test suite, which tested some hairy corner cases, are now defined to not be failures at all. The decisions: - Using non-string keys is undefined behavior; non-empty strings that are not valid as identifier according to the grammar are allowed: http://mail.python.org/pipermail/python-dev/2008-June/080309.html - String subclasses may be normalized to regular strings: http://mail.python.org/pipermail/python-dev/2008-June/080312.html - The restriction applies to both class dicts and instance dicts: http://mail.python.org/pipermail/python-dev/2008-June/080313.html - Frameworks currently using non-string attributes should change their behavior; http://mail.python.org/pipermail/python-dev/2008-June/080319.html - Willem

1 0

[clpython-devel] Computer Language Shootout benchmarks
by Rudolf 19 May '08

19 May '08

Has anyone had any luck running any of them? I just tried three (pidigts, nsieve, and recursive) and got some nice exceptions in return. Thanks -Rudolf Olah

2 1

[clpython-devel] Re: CLPython on SBCL
by Willem Broekema 03 May '08

03 May '08

Hello Bob, On Thu, May 1, 2008 at 5:52 PM, Robert Brown <brown(a)google.com> wrote: > I tried to get CLPython up and running on the latest SBCL. The diff below > contains a couple of easy fixes. SBCL wants BREAK's argument to be a > string > and SBCL's LOOP does not like a negative loop increment. Thanks for the patches! > The real porting problem right now is CLOS related. SBCL does not like > the > following code in core/classes.lisp: > > ;; Fix superclass and metaclass of PY-DICT. > (ensure-class 'py-dict > :direct-superclasses (list 'py-core-object) > :metaclass 'py-core-type) > > I get the following error: > > debugger invoked on a SB-PCL::METAOBJECT-INITIALIZATION-VIOLATION in > thread > #<THREAD "initial thread" {11701A79}>: > Cannot CHANGE-CLASS objects into CLASS metaobjects. > See also: > AMOP, Initialization of Class Metaobjects > > I think the problem is that PY-DICT is a normal class and the ENSURE-CLASS > call tries to turn it into a metaclass. Anyway, I'm far from a CLOS > expert. Well, class py-dict is not turned into a metaclass here, at least that's not the intention. :) The superclass and metaclass of it are changed but py-dict remains a non-metaclass class. So I think the actual error message is incorrect, but something else is wrong. The problem might be that you can not change the metaclasses of a class using ensure-class. Could you please check if the call to ensure-class without the metaclass change is accepted? (ensure-class 'py-dict :direct-superclasses (list 'py-core-object)) Thanks, - Willem

2 3

[clpython-devel] RE: CLPython on LispWorks
by Jochen Schmidt 22 Apr '08

22 Apr '08

Hello Willem, I've tried to compile CLPython as you suggested in your message. There were two problems I had to solve: 1) Incomplete Definition in core/csetup.lisp The only Definition in this file was: (defun py-raise (exc-type string &rest format-args) "Raise a Python exception with given format string" (if +exceptions-are-python-objects+ (error exc-type :args (cons string format-args))) (error exc-type I just closed the two open parens to get it compiling. If I understood the code right - the incomplete part of this function would not get taken by LispWorks anyways (because on LispWorks you did set +exceptions-are-python-objects+ to T). 2) Reader Problem in exceptions.lisp There are two definitions for {Exception}, depending on the value of +exceptions-are-python-objects+. The decision which of the definitions applies is done by a reader-conditional which is setup within the same EVAL-WHEN like the definitions themselves; this means that the definitions are already through the reader before you push :exceptions- are-python-objects on *features*. The solution is to split the EVAL- WHEN form into two: One to push :exceptions-are-python-objects on *features* and the second one with the definitions of {Exception}. Actually I think the {Exception}-Definition wouldn't have to be within an EVAL-WHEN at all. After this two points CLPython compiles through and it seems to run - impressive! I've run your test-suite and the only failure was this one: Test failed: known failure: (CLPYTHON.PARSER:PARSE "def f(a=3,): pass") Reason: detected an unexpected error of type `#<CLPYTHON::PY-TYPE CLPYTHON.USER.BUILTIN.TYPE.EXCEPTION:|SyntaxError| 21A26D3B>': SyntaxError: Parse error at line 1, at token `)'. Expected one of: `(' `identifier' `*' `**'. [Internal error #<YACC:YACC-PARSE-ERROR 200FC37F> caught due to CLPYTHON.PARSER::*CATCH-YACC-CONDITIONS*] Which - as I understood the message - is a already known problem. Again: CLPython is a really impressive bit of work! Thanks for sharing it with us. ciao, Jochen Schmidt -- Jochen Schmidt CRISPYLOGICS Julienstr. 1, 90419 Nuremberg Fon +49 (0)911 517 999 82 Fax +49 (0)911 517 999 83 mailto:info@crispylogics.com http://www.crispylogics.com

2 1

[clpython-devel] CLPython on LispWorks
by Willem Broekema 01 Apr '08

01 Apr '08

Dear list members, In the last few days I made CLPython more portable, so that it now runs on LispWorks too! If you have LispWorks, please give it a try and let me know if you encounter any problems. In particular I'd like to hear if the unit test runs fine for you, too. Once that is verified, I'll update the outdated web page with the new status, and call this "CLPython 1.0". Please take these steps: 1. Download CLPython from CVS: cvs -d :pserver:cvspublic@cvspublic.franz.com:/cvs-public login Password: cvspublic cvs -d :pserver:cvspublic@cvspublic.franz.com:/cvs-public checkout clpython 2. Download the test framework "ptester" (the portable version of Allegro's "tester") from http://files.b9.com/ptester/ptester-latest.tar.gz and install that asdf system. 3. Load the :clpython asdf system: (asdf:operate 'asdf:load-op :clpython) 4. Run the CLPython unit tests: (asdf:operate 'asdf:test-op :clpython) The unit test should finish with the message "Errors detected in this test: 5" (which are 5 known issues) and several hundred test successes. Please let me know how this works for you. Also, start up the Python REPL with (clpython:repl) and start typing :-) Cheers, - Willem

1 0

[clpython-devel] inline
by Jones, Eric SPC MIL USA FORSCOM 20 Mar '08

20 Mar '08

This may be a bit of the topic but would support for in-lining be acceptable or even just close interoperability of the two languages. Python and Lisp are similar but some pieces of code are more easily implemented in one or the other. Maybe something like: (LISP CODE) (LISP CODE) :@python python code python code :@PYTHON (LISP CODE) (LISP CODE)

2 1

[clpython-devel] Status?
by Rudolf 16 Jan '08

16 Jan '08

Heya, I just stumbled upon CLPython today. What's the status of it? Is there *any* sort of development going on? What would be a good place, for a CL newbie, to start adding functionality from this list: http://common-lisp.net/project/clpython/status.html Thanks, Rudolf

4 5

[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

[clpython-devel] CLPython for other lisps
by Michel Van den Bergh 04 Feb '07

04 Feb '07

Hi, Is there any hope that CLPython will be ported to other lisps (gcl, clisp, sbcl)? I have been advocating python as a language for maxima. Maxima (maxima.sf.net) is a very powerful GPL'ed computer algebra system that is written in CL. On top on the underlying CL implementation it also supports an algol like programming language ("the maxima language") which however has serious problems (you can check the discussions on the maxima mailing list about this). I think that it would be good to have python available as a second (algol like) language for maxima. Python is a widely known language with well understood semantics. It seems that CLPython would fit the bill but unfortunately the fact that it runs only on one CL implementation makes it impossible to use. For portability maxima has to run on all available CL implementations (and has admirably succeeded in doing so up to now). Best regards, Michel

3 4

[clpython-devel] CVS module renamed to "clpython"
by Willem Broekema 30 Jan '07

30 Jan '07

The CLPython source code is stored in a cvs repository at Franz. Until now the cvs module was named "python". The module has now been renamed to "clpython", the official name of this project. To retrieve the code under the proper module name: cvs -d :pserver:cvspublic@cvspublic.franz.com:/cvs-public login (use password: cvspublic) cvs -d :pserver:cvspublic@cvspublic.franz.com:/cvs-public checkout clpython Of course these instructions are also on http://trac.common-lisp.net/clpython There is more reorganization coming up, in terms of directory structure and packages. I'll describe that when it is submitted, in a few days. Cheers, - Willem

1 0

[clpython-devel] Fwd: Not dead, bold future
by Willem Broekema 17 Dec '06

17 Dec '06

Link to message: http://groups.google.com/group/comp.lang.python/msg/7629a87adac6d0b1 ---------- Forwarded message ---------- From: Willem Broekema <metawilm(a)gmail.com> Date: Dec 13, 2006 8:28 PM Subject: Re: merits of Lisp vs Python To: Paul Rubin wrote: > Does this count as a "children of a lesser Python"? This sounds like a quite derogatory first question. CLPython is not a dead and abandoned project, nor is execution speed its main goal, nor are Python semantics bended anywhere (it can run the Pie-thon benchmark). Sure, some recently introduced language features are missing, but with just a little effort that's solved... Moreover, in Common Lisp source code analysis and manipulation can be expressed easily. CLPython thus provides ample opportunities to analyze type inference or caching schemes. Most of that is unexplored territory, I think. I like the journey so far. > How does clpython implement Python's immutable strings, for example? Normal Python strings are represented by normal Lisp strings. Instances of subclasses of 'str' are represented by CLOS instances. That's for performance reasons. This dual-representation aspect is nicely hidden behind macros, so that even in the code of CLPython itself there's no need to worry, or even know, about it. Why not take a look in the code -- I'll be happy to explain things. - Willem

1 0

[clpython-devel] Fwd: CLPython objects in a Lisp image
by Willem Broekema 17 Dec '06

17 Dec '06

Link to message: http://groups.google.com/group/comp.lang.python/msg/b72788cc5569d778 ---------- Forwarded message ---------- From: metawilm(a)gmail.com <metawilm(a)gmail.com> Date: Dec 16, 2006 12:54 PM Subject: Re: CLPython (was Re: merits of Lisp vs Python) To: Paul Rubin wrote: > metawilm(a)gmail.com writes: > > > a = 'hello' > > > a[0] = 'H' # attempt to change first letter to upper case > > > > As CLPython mirrors Python semantics, this results in a TypeError. The > > internal representation of an immutable Python string is a mutable Lisp > > string, but there is no way you can actually modify it from within CLPython. > > How do you manage that? The compiler can't check. Is there some kind > of special dispatch on the assignment statement instead of turning it > into a setf? Indeed, the assignment of subitems is dynamically dispatched, and always goes via __setitem__ methods, as specified in the language. The __setitem__ methods for strings and tuples raise exceptions. The ones for lists and vectors could be translated into a simple (setf (aref ..) ..) and (setf (nth ..) ..), unless the index is actually a slice and actually a subsequence must be replaced. Now, the above description using __setitem__ methods is how it apparently works, as observed from the outside. Internally there is a generic function (setf py-subs) that does the work itself, skipping the lookup and calling of __setitem__, if the object is a vector or dict. (The user can call x.__setitem__ explicitly, so that method must exist internally.) Maybe you were thinking that CLPython, given Python code, outputs a big pile of self-contained equivalent Lisp code that can be run independently, and then CLPython is finished. Instead, only a small amount of Lisp code is generated, but that code can only be run when the CLPython environment is loaded. The generated code refers to that environment, e.g. s[0] = 'x' is translated into a call to (setf (py-subs ..) ..), and function (setf py-subs) is part of the CLPython environment that must be loaded at run-time. If you compile a Python function, the result is a (mostly) normal Lisp function - its origin from the Python world does not really matter. Also, all Python data structures are first-class Lisp data. Thus CLPython objects live happily together with "normal" Lisp objects in the same image. And now we arrive at the most exciting part: other Lisp libraries can be loaded in the same image, and we can create connections. Like, after loading CLIM and defining how CLPython objects should be presented, we should get a Python interpreter where classes are displayed graphically and where you can inspect and modify them by mouse. Imagine that you have interactively added a method to a class by dragging a function to a class, then being able to right-click and select "write method", which will write the definition of the method in the right place in the class definition source code in your Climacs (CLIM-based Emacs) buffer. That's the kind of features I have in mind, and the best thing is that conceptually a lot of the work consists of connecting dots that already out there. But as there are so many of them, a few extra pencils would be quite welcome <wink> - Willem

1 0

[clpython-devel] Fwd: Choice of Common Lisp
by Willem Broekema 17 Dec '06

17 Dec '06

Link to message: http://groups.google.com/group/comp.lang.python/msg/fbfdc12acddc0f3f ---------- Forwarded message ---------- From: metawilm(a)gmail.com <metawilm(a)gmail.com> Date: Dec 15, 2006 8:23 PM Subject: Re: CLPython (was Re: merits of Lisp vs Python) To: Paul Rubin wrote: > I thought it was of some interest though I'm a little surprise by the > choice of CL rather than Scheme as a target. In many aspects Python is a subset of CL. In CLPython, exceptions are Lisp conditions with a custom metaclass (strictly spoken not portable CL), Python (meta)classes are CLOS classes, methods are implemented using hashtables and functions and CLOS generic functions, strings and numbers have direct equivalents, hash tables implement dicts, Python functions are funcallable CLOS instances, tuples and lists are Lisp lists and vectors, generators are closures. Thus a great part of implementing CLPython consisted of connecting already existing dots. I found that quite amazing. > I'm still not sure about the mapping of Python strings to Lisp strings. > What happens with the following in CLPython? > > a = 'hello' > a[0] = 'H' # attempt to change first letter to upper case As CLPython mirrors Python semantics, this results in a TypeError. The internal representation of an immutable Python string is a mutable Lisp string, but there is no way you can actually modify it from within CLPython. Now in some cases modifying strings is dangerous (e.g. when stored in an instance dict to represent an attribute), but in other cases it can be completely safe. And modifying strings is a normal Lisp feature, so it sounds strange to disallow it at all times. Maybe there should be a way for the user to declare that he knows what he is doing, and does not want the Python implementation to be "crippled" w.r.t. the host language. Normally you start the CLPython interpreter using (repl); maybe something like this would allow dangerous statements: (let ((*strict-python-semantics* nil)) (repl)) Oh, and there is actually one way to modify Python strings in the interpreter, namely using Lisp commands: PYTHON(12): (repl) [CLPython -- type `:q' to quit, `:help' for help] >>> s = "abc" 'abc' >>> (setf (aref _ 0) #\x) #\x >>> s 'xbc' >>> type(s) #<class PY-STRING @ #x10575342> >>> type(s) == str 1 >>> s 'xbc' >>> (inspect _) A NEW simple-string (3) "xbc" @ #x11548f6a 0-> The character #\x [#x0078] 1-> The character #\b [#x0062] 2-> The character #\c [#x0063] [1i] PYTHON(13): :ptl >>>

1 0

[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