marcoheisig/cl4py issues and pull requests

#26 - Delay deleting handles until the next Lisp.eval call

Pull Request - State: closed - Opened by Gleefre about 1 month ago

#25 - Data race in LispWrapper's finalizer

Issue - State: closed - Opened by Gleefre about 1 month ago - 5 comments

#24 - Runtime error parsing token

Issue - State: closed - Opened by dmenager about 1 year ago - 9 comments

#23 - run-program is undefined

Issue - State: open - Opened by craigkrais almost 3 years ago

#22 - Unbound variable error while loading .lisp file

Issue - State: closed - Opened by craigkrais about 3 years ago - 2 comments

#21 - Callbacks?

Issue - State: closed - Opened by rpgoldman over 3 years ago - 1 comment

#20 - Should we print readably?

Issue - State: closed - Opened by rpgoldman almost 4 years ago - 3 comments

#19 - WIP: Travis test script.

Pull Request - State: closed - Opened by rpgoldman about 4 years ago - 2 comments

#18 - Wishlist: easier way to set variables

Issue - State: closed - Opened by rpgoldman about 4 years ago - 1 comment

#17 - Add option for backtrace on runtime errors

Pull Request - State: closed - Opened by rpgoldman about 4 years ago

#16 - Unable to get backtrace to work...

Issue - State: closed - Opened by rpgoldman about 4 years ago - 2 comments

#15 - Can we assume ASDF/UIOP?

Issue - State: closed - Opened by rpgoldman about 4 years ago - 1 comment

#14 - Macros not available in cl4py

Issue - State: closed - Opened by rpgoldman over 4 years ago - 1 comment

#13 - Macros are not available through CL4PY

Issue - State: closed - Opened by rpgoldman over 4 years ago - 2 comments

#12 - What is a `<cl4py.lisp.function object at 0x1167ef650>`?

Issue - State: open - Opened by rpgoldman over 4 years ago - 2 comments

#11 - Ignore irrelevant files.

Pull Request - State: closed - Opened by rpgoldman over 4 years ago

#10 - Allow use others implementations than SBCL

Issue - State: closed - Opened by noloop over 4 years ago - 2 comments

#9 - Control the use of the cl4py readtable.

Pull Request - State: closed - Opened by rpgoldman over 4 years ago - 7 comments

#8 - Request for advice: Lisp Backtraces

Issue - State: closed - Opened by rpgoldman over 4 years ago - 5 comments

#7 - Expand the set of examples.

Pull Request - State: closed - Opened by rpgoldman over 4 years ago - 1 comment

#6 - Error when importing cl4py under windows 10

Issue - State: closed - Opened by scorpion81 over 4 years ago - 3 comments

#5 - BrokenPipeError with clisp2.49 python3.5

Issue - State: closed - Opened by pulinagrawal over 5 years ago - 2 comments

#4 - Turn Python keyword arguments into Lisp keyword arguments

Pull Request - State: closed - Opened by scymtym over 5 years ago - 1 comment

#3 - Stack exhaustion when sending/receiving large data structures

Issue - State: open - Opened by marcoheisig almost 6 years ago - 1 comment

#2 - Small issues in README

Issue - State: closed - Opened by Bike almost 6 years ago - 1 comment

#1 - About the way to load lisp libraries

Issue - State: closed - Opened by t-cool about 6 years ago - 2 comments

Ecosyste.ms: Issues

GitHub / marcoheisig/cl4py issues and pull requests