<html><head></head><body><div class="ydpd263c801yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false"><div><div dir="ltr" data-setdir="false">I'm not sure I'd want a clone of a
Python style API; I'd rather have something that's idiomatic lisp. I
like Marco's idea of a spec, however beyond documentation (and that is
valuable), it mostly means we can have multiple implementations, and I
suspect they'd end up like everything else, half-baked, poorly documented implementations of the spec.<br></div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I
think we can do a lot of useful work without cloning the entire Numpy
API. The real challenge, IMO, is what Marco outlines below. Getting the
community to rally behind a single implementation that they didn't cook
up themselves in their garage whilst watching TV and drinking beer. NIH
disease runs rampant. There are however enough high-quality starting points (libraries) that might be worth looking at. I think tpapp's stuff is good, with generally small codebase and an API worked out via actual usage in a real-world environment.<br></div><div><br></div><div dir="ltr" data-setdir="false">Cheers,</div><div dir="ltr" data-setdir="false"> Steve<br> </div></div><div><br></div></div><div><br></div>
</div><div id="yahoo_quoted_1620298256" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Tuesday, April 11, 2023 at 05:19:25 AM GMT+8, Marco Antoniotti <marco.antoniotti@unimib.it> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv6827228025"><div><div dir="ltr"><div>IMHO, it'd be easier and effective to band up together and FIRST write a proper API specification and THEN implement it in CL.<br clear="none"><br clear="none"></div><div>But Common Lispers are like academics: the "herding cats" applies.</div><div><br clear="none"></div><div>Cheers</div><div><br clear="none"></div><div>Marco<br clear="none"><br clear="none"></div><div>PS I am a Common Lisper AND an academic. You know what I mean...<br clear="none"></div><div><div><br clear="none"></div><div><br clear="none"></div></div></div><br clear="none"><div id="yiv6827228025yqt65590" class="yiv6827228025yqt3327084100"><div class="yiv6827228025gmail_quote"><div dir="ltr" class="yiv6827228025gmail_attr">On Mon, Apr 10, 2023 at 9:09 PM Robert Goldman <<a rel="nofollow noopener noreferrer" shape="rect" ymailto="mailto:rpgoldman@sift.info" target="_blank" href="mailto:rpgoldman@sift.info">rpgoldman@sift.info</a>> wrote:<br clear="none"></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;" class="yiv6827228025gmail_quote">Has anyone taken the Numpy C API and created a CFFI library based on it? I see some attempts to clone it in pure CL, but I would guess that just using it through its API might be easier and more effective.<br clear="none">
<br clear="none">
<br clear="none">
</blockquote></div></div>
</div></div></div>
</div>
</div></body></html>