From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Guile User <guile-user@gnu.org>, Mikael Djurfeldt <mikael@djurfeldt.com>
Subject: Re: [Compiler Tower] A better Python plan
Date: Sat, 14 Dec 2024 11:47:50 +0100 [thread overview]
Message-ID: <CAA2XvwLDBjt2XVKEMucCoSuCxM8F9fEo4JhsQLmzjj1e5FKkMA@mail.gmail.com> (raw)
In-Reply-To: <CAA2XvwKoJqH6i-tEvTZeWvDtj1XUXdMd65Qdq3ZvS=PB-RDWWA@mail.gmail.com>
Being able to script in Python in Guile would be the strongest yet showcase
for multi-language support in Guile and would be an additional strong
argument for Guile in Emacs.
Den lör 14 dec. 2024 11:23Mikael Djurfeldt <mikael@djurfeldt.com> skrev:
> While this is interesting, I'd like to have support for Python proper,
> with support for Python C interface such that it is possible to load Python
> extensions.
>
> Stefan Israelsson Tampe previously implemented Python in Guile
> https://gitlab.com/python-on-guile/python-on-guile/
>
> I've tested it and it's possible to load many Python modules in that
> framework. However, it might be that Python support needs a redesign and
> rewrite. Perhaps it is then possible to fetch some insights and inspiration
> from Stefans work?
>
> Best regards,
> Mikael
>
> On Sat, Dec 14, 2024 at 7:38 AM Nala Ginrut <nalaginrut@gmail.com> wrote:
>
>> Recently I've heard about Starlark, which is described as "Starlark is a
>> dialect of Python. Like Python, it is a dynamically typed language with
>> high-level data types, first-class functions with lexical scope, and
>> garbage collection."
>>
>> I think it could be easier than implementing original Python.
>> https://github.com/laurentlb/awesome-starlark
>>
>> Best regards.
>>
>
next prev parent reply other threads:[~2024-12-14 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 6:37 [Compiler Tower] A better Python plan Nala Ginrut
2024-12-14 10:23 ` Mikael Djurfeldt
2024-12-14 10:47 ` Mikael Djurfeldt [this message]
2024-12-14 11:08 ` Nala Ginrut
2024-12-14 11:16 ` Mikael Djurfeldt
2024-12-14 12:03 ` 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=CAA2XvwLDBjt2XVKEMucCoSuCxM8F9fEo4JhsQLmzjj1e5FKkMA@mail.gmail.com \
--to=mikael@djurfeldt.com \
--cc=guile-user@gnu.org \
--cc=nalaginrut@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).