From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Project scheme-python
Date: Thu, 17 Sep 2020 08:50:42 +0200 [thread overview]
Message-ID: <aeed1e4e-0d1d-bce8-5c45-a14f03e6ce19@posteo.de> (raw)
In-Reply-To: <CAGua6m0Bxh=uPWSKJRouEYpkB02gFopwT+2v9oXJLH6=f0PtBg@mail.gmail.com>
Hi Stefan!
Can you explain a little more how it is used?
If I understand correctly, one could write Scheme code, but with forms,
which implement (by themselves or in some combination) Python keywords
or Python semantics. You mentioned, that it does not have a Python
compiler. So there is no way of translating Python into the Scheme code
for those modules. Basically that is a different concern, separation of
concerns, modularization, better maintainability, etc.?
Do you have an example project, where this separated code is used in?
Regards,
Zelphir
On 12.09.20 19:59, Stefan Israelsson Tampe wrote:
> Hi,
>
> I am the author of python-on-guile and I just took out the scheme
> infrastructure for python and put it is a self contained project of not too
> large size. It does not have a python compiler and cannot use python code.
> So scheme only.
>
> You can find the project at
>
> docs for the interfaces is mostly documented at,
> http://c-lambda.se/python-on-guile/
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2020-09-17 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 17:59 Project scheme-python Stefan Israelsson Tampe
2020-09-17 6:50 ` Zelphir Kaltstahl [this message]
2020-09-19 20:25 ` Stefan Israelsson Tampe
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=aeed1e4e-0d1d-bce8-5c45-a14f03e6ce19@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
--cc=stefan.itampe@gmail.com \
/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).