From: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>
To: caml-list@inria.fr
Subject: [Caml-list] pycaml
Date: Thu, 5 Mar 2015 12:17:43 +0100 [thread overview]
Message-ID: <20150305111743.GA2334@pl-59055.rocqadm.inria.fr> (raw)
Dear all,
Does anybody here know about pycaml's maintainance status, please?
Being involved in a project that depends on it, I'd be happy to
participate to its maintainance but am not sure how to do since it's not
clear to me who maintains the project currently, if there is someone
maintaining it at all.
More generally speaking, is there interest in bridging OCaml and Python?
Are other solutions (perhaps more maintained) than pycaml arond?
Thanks for any feedback!
Sébastien.
next reply other threads:[~2015-03-05 11:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 11:17 Sébastien Hinderer [this message]
2015-03-05 15:52 ` Drup
2015-03-05 16:09 ` John Whitington
-- strict thread matches above, loose matches on Subject: below --
2015-03-06 14:04 Nils Becker
2011-10-05 18:52 [Caml-list] Pycaml Thomas Fischbacher
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150305111743.GA2334@pl-59055.rocqadm.inria.fr \
--to=sebastien.hinderer@inria.fr \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).