From: Stefano Zacchiroli <zack@upsilon.cc>
To: Caml-list List <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml and PETSc
Date: Fri, 23 Jan 2009 15:42:27 +0100 [thread overview]
Message-ID: <20090123144227.GA27540@usha.takhisis.invalid> (raw)
In-Reply-To: <4979CF93.3060908@soton.ac.uk>
On Fri, Jan 23, 2009 at 02:09:23PM +0000, Dr. Thomas Fischbacher wrote:
>> Is there no maintained upstream source for Pycaml? I noticed the
>> other day that Coccinelle is also shipping Pycaml, and their version
>> doesn't work with Python 2.6 (potential patch attached).
>
> We repeatedly tried to contact the author (Art), but did not succeed.
> So, in the end, we just adopted and extended it.
Thanks for that!
Still, instead of embedding your extensions within coccinelle, what
about maintaining it (or at least realising it once) as the separate
project it deserves to be?
I've kind of a deja-vu with this, with someone else in the past taking
care for a little while of pycaml, but never reaching the outcome of
making a new release taking over its maintenance.
Would you be so kind of going forward with that?
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
next prev parent reply other threads:[~2009-01-23 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 19:09 Dr. Thomas Fischbacher
2009-01-22 23:45 ` [Caml-list] " Alexy Khrabrov
2009-01-23 13:20 ` Richard Jones
2009-01-23 14:09 ` Dr. Thomas Fischbacher
2009-01-23 14:42 ` Stefano Zacchiroli [this message]
2009-01-26 9:17 ` RABIH.ELCHAAR
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=20090123144227.GA27540@usha.takhisis.invalid \
--to=zack@upsilon.cc \
--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).