From: Anderson Lizardo <anderson.lizardo@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: pysparse: Python bindings for sparse
Date: Tue, 26 May 2009 21:38:25 -0400 [thread overview]
Message-ID: <5b5833aa0905261838r6ddfb0f4xa343f787c47e4f40@mail.gmail.com> (raw)
Hi,
I am proud to announce the availability of pysparse, that consists of
Python bindings for sparse. It can be obtained from:
http://gitorious.org/pysparse/pysparse
Please note it is the initial commit, and many things are missing (see
the TODO section on the README). But I've already added enough support
to port test-dissect, test-lexing and test-linearize to python, and
they work just fine :)
My plans are to add support for more functions incrementally as I
become more familiar with the current public sparse API.
Comments, suggestions and contributions are welcome. Note that I've
intentionally licensed pysparse under the MIT license so that it can
be added to a future sparse release licensed under it (if the sparse
maintainers want so). But for now pysparse can live outside sparse
tree just fine.
Thanks,
--
Anderson Lizardo
Instituto Nokia de Tecnologia (INdT)
Manaus - Brazil
reply other threads:[~2009-05-27 1:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5b5833aa0905261838r6ddfb0f4xa343f787c47e4f40@mail.gmail.com \
--to=anderson.lizardo@gmail.com \
--cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).