pynie-dev team mailing list archive

[John Rizzo <johnrizzo1@xxxxxxxxx>]

Well so far I've been able to check out both pynie and puffin and made a
few updates which allowed them both to build.  Now I'm trying to understand
how both work and see if I'm brave enough to complete/merge the puffin work
into pynie.  I have no idea if that is the best course of action but I'm
sure as I start to gain a better understanding I'll be able to see what
really needs to be done.

It was a bit confusing given all the locations for code, documentation, etc.

https://launchpad.net/~pynie-dev
https://bitbucket.org/allison/pynie
https://bitbucket.org/lucian1900/puffin
http://code.google.com/p/pynie/
http://pynie.googlecode.com/svn/trunk/

I wasn't sure which was exactly the latest but I forked both allison's
pynie from bitbucket and lucian1900's puffin from bitbucket and I'm doing
my work in those forks.  Feel free to take a look at my work but don't
expect too much just yet.  I'm still learning.

https://bitbucket.org/johnrizzo1/pynie
https://bitbucket.org/johnrizzo1/puffin

John Rizzo
johnrizzo1@xxxxxxxxx


On 4 February 2012 17:32, Sean Smith <smsmith@xxxxxxxxx> wrote:

> I once had this same ambition. Then I lost the time I had planned to use
> for pynie. I could be a casual contributor if significant development picks
> up.
>
> Where I left off, I was learning that some internal objects from perl6
> were reused for pynie unchanged. However, some of their built-in behaviors
> did not match python's expected behaviors. I wanted to be able to share
> data directly with perl6 at runtime, so using the same object types was
> good, but I couldn't figure out how to reuse the same objects and define
> different behaviors for things like string conversion, Boolean conversion,
> etc.
>
> I also hadn't quite understood the machinery used to do parsing and so on.
> There was an awful lot of thinly documented magic at work there.
>
> All of this was years ago. Much may have changed since then. Please do
> report back what you find. I hope you inspire me to try again.
>
> - Sean
>
> On Feb 4, 2012, at 6:01 AM, John Rizzo <johnrizzo1@xxxxxxxxx> wrote:
>
> I'm definitely interested in contributing to get python on parrot.  I'm
> trying to learn more about language design in general and the relationship
> between the language, compiler and kernel/vm.
>
> I'm going to check it out today and try to get familiar with the code
> base.  Do you guys ever hang on irc?  I'm in the UK but I'll try to stay on
> the irc channel and see if anyone is around.
>
> John Rizzo
> johnrizzo1@xxxxxxxxx
>
>
> On 3 February 2012 07:54, Allison Randal <allison@xxxxxxxxxxx> wrote:
>
>> On 01/16/2012 06:23 PM, John Rizzo wrote:
>> > Hey guys I am interested in language development and I was looking at
>> > Parrot and Pynie.  Before I go too far down the rabbit hole I was
>> > wondering if this project is still active.  The last commit appears to
>> > be from Feb 2010.
>>
>> It's in suspended animation. We put it on hold for some changes in the
>> Parrot tool chain. Look at Puffin (Google Summer of Code project) for
>> the most recent work on Python on Parrot:
>> https://bitbucket.org/lucian1900/puffin. The general idea of Puffin was
>> to try out a new approach, and then restart Pynie along those lines if
>> it worked out well.
>>
>> If you're interested in contributing to Python on Parrot, I'd be happy
>> to help you get started. But, if you're looking for a model to use as a
>> base for implementing some other language, then I'll point you at other
>> projects depending on the kind of language you're interested in.
>>
>> Allison
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~pynie-dev
>> Post to     : pynie-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~pynie-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "pynie.dev" group.
>> To post to this group, send email to pynie-dev@xxxxxxxxxxxxxxxx.
>> To unsubscribe from this group, send email to
>> pynie-dev+unsubscribe@xxxxxxxxxxxxxxxx.
>> For more options, visit this group at
>> http://groups.google.com/group/pynie-dev?hl=en.
>>
>>
>  _______________________________________________
> Mailing list: https://launchpad.net/~pynie-dev
> Post to     : pynie-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~pynie-dev
> More help   : https://help.launchpad.net/ListHelp
>
>