From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: Python on guile
Date: Fri, 28 Feb 2020 23:22:34 +0100 [thread overview]
Message-ID: <CAGua6m1R7DDHkqVXS3bbzgQTNOGQCvUmFpRsjcBbH=Ae9OFZSg@mail.gmail.com> (raw)
Hi all, there is an ever stream of tickets to fix in the python clone made
in guile. Usually I spend time testing some python submodule and in the
process realizes issues with the current code base. I'm certain that there
is quite a lot of bus still remaining.
My latest addition was the subprocess module, which exersisced the select
code, the os module and a popen like implementation. In the process
glitches in the name spacing was found and fixed for classes. (the name
bounding in clasdefs are a let construct but the decorators can refer to
the variable bindings (methods and assignments). I fixed the try exception
mechanism when one issues a simple (raise). If in a contexts of a error
handler, then the catched exception is resent. previously a simple
Exception with no data was resent. Now most warnings that was spamming the
python session have been quited. quite a lot of bugs have been found in the
os module and fixed.
With this I'm happy with the python on guile repo and just released a
version 1.1
Repo:
https://gitlab.com/python-on-guile/python-on-guile/tree/master
Happy hacking
next reply other threads:[~2020-02-28 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 22:22 Stefan Israelsson Tampe [this message]
2020-03-02 3:16 ` Python on guile Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2020-03-22 21:28 Stefan Israelsson Tampe
2020-03-23 16:54 ` Arne Babenhauserheide
2014-08-09 12:58 python " Federico Beffa
2014-08-13 5:43 ` Nala Ginrut
2014-08-13 7:54 ` Jan Wedekind
2014-05-30 21:33 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='CAGua6m1R7DDHkqVXS3bbzgQTNOGQCvUmFpRsjcBbH=Ae9OFZSg@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--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).