unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Federico Beffa <beffa@ieee.org>
Cc: guile-user@gnu.org
Subject: Re: python on guile
Date: Wed, 13 Aug 2014 13:43:09 +0800	[thread overview]
Message-ID: <1407908589.24954.23.camel@Renee-desktop.suse> (raw)
In-Reply-To: <CAKrPhPM81wLrpmajHLD-XhfS7aumu-Ytz7O4GimRwaLfXbfOVA@mail.gmail.com>

On Sat, 2014-08-09 at 14:58 +0200, Federico Beffa wrote:
> > On Fri, 2014-05-30 at 23:33 +0200, Stefan Israelsson Tampe wrote:
> >> I would like to hijack the python2/3 community over to guile.
> 
> Hi, I'm a user of python which would very much prefer to use Scheme :-)
> 
> I just wanted to say that the reason for which a lot of
> engineers/scientists are using python, is because it now provides a
> pretty large set of scientific/engineering and plotting functions with
> the 3 main libraries numpy, scipy and matplotlib. It would be
> fantastic if somehow this functionality could be made available in
> guile :-)
> 

I agree with you, the popular of Python is largely because of some
popular libs.


I'm one of the guys who is interested in hacking multi-lang front-end on
Guile. And I think there're at least two approaches to cut this Gordian
Knot.

1. Make great effort to be compatible with the original Python, even the
C interfaces(maybe a wrapper or refactor the C part with Guile CAPIs).
And recompile the whole numpy/scipy/matplotlib with guile-python. This
would be the fantastic and idealism way. But challenging.
One of the reasons is whether our brand new CPS-based backend (in master
branch) is suitable for Python language would be suspended. In
principle, it's suitable for FP languages especially continuation-based
one. But it's worth to try anyway.
The difficulty contains both workload and indeterminacy.

2. Write Guile own libs for the same purpose of numpy/scipy/matplotlib,
and users may call the related modules from Python code. I have to
emphasize that any language implemented on Guile could call the modules
written with other languages, if it's on Guile too.
This is also challenging. But IMO, the difficulty of this way contains
workload only.


These are my ideas. And I'd like to try the first way because of my
hacking habit.
But the most significant thing is to make the latest Guile-2.2(in master
branch) better than before. I'm trying to rewrite guile-lua on
Guile-2.2, but it's in a slow progress since there're lot of new stuffs
need to learn.

Any ideas?
 

Best regards.





  reply	other threads:[~2014-08-13  5:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-09 12:58 python on guile Federico Beffa
2014-08-13  5:43 ` Nala Ginrut [this message]
2014-08-13  7:54   ` Jan Wedekind
  -- strict thread matches above, loose matches on Subject: below --
2020-03-22 21:28 Python " Stefan Israelsson Tampe
2020-03-23 16:54 ` Arne Babenhauserheide
2020-02-28 22:22 Stefan Israelsson Tampe
2020-03-02  3:16 ` Maxim Cournoyer
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=1407908589.24954.23.camel@Renee-desktop.suse \
    --to=nalaginrut@gmail.com \
    --cc=beffa@ieee.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).