[schemepy] Finished porting pyscheme to the Schemepy interface

[schemepy] Finished porting pyscheme to the Schemepy interface

Chiyuan Zhang pluskid at gmail.com
Sun May 18 12:06:50 EDT 2008


On Sat, May 17, 2008 at 7:12 PM, Tim Ansell <mithro at mithis.com> wrote:
> Hello,
>
> It might be a good idea to move the "port tpxxxx to schemepy" task
> forward. This will allow you to test the interface in a more real world
> situations.
I'm also thinking about that.
>
> As you have just had a lot to deal with pyscheme, it would be a good
> time to do the conversion while the differences are sharp in your mind.
>
> I'm thinking the most likely candidate would be tpclient-pywx (which
> actually means libtpclient-py). I'm happy to give you a branch for you
> to do the testing on.
So is it that libtpclient-py is the Python client that is using
pyscheme? I'm not familiar with Thousand Parsec yet. I guess the TP
client is using embedded Scheme to allow users to write their own
script/extension, is that true? And is it necessary to learn how to
use the client? Or is there some existing test suites that I can just
run to ensure that I didn't break something?

I'm sure it would be a good idea to use Schemepy in a real world
project. :)
>
> Tim 'Mithro' Ansell
>
> On Thu, 2008-05-15 at 19:14 +0800, Chiyuan Zhang wrote:
>> Here's the task report:
>>
>>
>> Make pyscheme confront with the new Schemepy front-end interface
>> ----------------------------------------------------------------------
>>                                                 planned at: 2008-05-08
>>
>> Then we could compare the performance between other back-ends and the
>> fall-back back-end.
>>
> <snip>
>
> _______________________________________________
> schemepy mailing list
> schemepy at thousandparsec.net
> http://mail.thousandparsec.net/tp/mailman.php/listinfo/schemepy
>



-- 
pluskid


More information about the schemepy mailing list