unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: guile-devel <guile-devel@gnu.org>, Guile User <guile-user@gnu.org>
Subject: Python on guile
Date: Sun, 22 Mar 2020 22:28:01 +0100	[thread overview]
Message-ID: <CAGua6m0Z=9VzDs0wWSkJo7QxE-yQYf-zDB2gcS98ssiZ0LdFnA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

Hi all,

Now in corona times I'm working quite a lot with python-on-guile fixing
bugs in the parser and compiler. Trying to add and test more python
modules. My test case is to get IPython running on python on guile. Some of
the python library code is very advanced python so getting it working is a
great test case. My latest addition is to generate AST from python code. I
have an AST of my own but the translation is quite transparent. I also
managed to get the python typing.py module compiling and running. That was
quite a challenge as it is quite a lot af meta programming that was hard to
get working. I also have been working hard to get autocompilation of python
code working for guile 3.0.0 and are quite happy now with it. I also
sielenced a lot of variable warnings that was wrong. So no usually those
warnings are spot on and very helpful. I will continue to work on getting
better feedback in the compiler to detect errors. I also want to see if I
can do anything with the ctypes package as well. I think the gule ffi is
comparable to ctypes. Else I will continue to see what I can do with the
ipython package.

Happy Hacking

[-- Attachment #2: Type: text/html, Size: 1218 bytes --]

             reply	other threads:[~2020-03-22 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-22 21:28 Stefan Israelsson Tampe [this message]
2020-03-23 16:54 ` Python on guile Arne Babenhauserheide
  -- strict thread matches above, loose matches on Subject: below --
2014-05-30 21:33 python " Stefan Israelsson Tampe
2014-06-03  6:28 ` Nala Ginrut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGua6m0Z=9VzDs0wWSkJo7QxE-yQYf-zDB2gcS98ssiZ0LdFnA@mail.gmail.com' \
    --to=stefan.itampe@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).