Kevin Tew wrote:
Sam Ruby wrote:
So why won't Michal Wallace sign over the copyright?Kevin Tew wrote:
Sam,
Just wondering what the status is on python/parrot/pirate/pyrate.
These both look outdated. http://www.intertwingly.net/stories/2004/10/05/pyrate.zip http://pirate.versionhost.com/viewcvs.cgi/pirate/
I haven't looked at it for a few months now. I do plan to revisit it enough to get the Pie-thon tests completed by the time of OSCON (in August).
Is there a up to date cvs repo?
http://pirate.tangentcode.com/
Can we get this code checked into the parrot svn repo?
Unfortunately, no. Much of this code is copyright Michal Wallace.
The good news is that the "good stuff" is in the parrot repo already. What is left - a simple translator - can and should, IMHO, be recoded into Perl6 once enough of that is running.
- Sam Ruby
I talked to Michal briefly about this a while back. My impression was that he wanted to sign over the copyright to the Python foundation. Which makes a bit of sense - the goal of having everything run on a single runtime does not necessarily imply that everything has to be owned by a single organization and put into a single repository.
My own opinions is that Michal thinks too much. ;-)
My impression is that everybody here is reasonable, and if it made sense for further development to be transferred to another organization, then some reasonable arrangement would be made.
Also, I believe that much of the initial work is throwaway work anyway. Build one to throw away, and all that.
Cool I did notice all the python pmcs.
By translator I assume you mean a interpreter/compiler to parrot byte code.
At the moment, it is to Python to IMC, but eventually going directly to bytecode would be a good idea.
Why would you do it in Perl6, why not self hosted in python?
Self hosted in Python is a good idea, once it can be bootstrapped.
Overview of the current process:
1) Leverage python's "compiler" class to convert source to AST 2) Pirate converts AST to IMC 3) Parrot converts IMC to bytecode
I'm thinking of toying around with python and just want to leverage all the previous work.
Excellent. In the meantime, if you are interested in getting commit access to the Pirate repository, I'm confident that that can be arranged.
My feeling, for what it is worth, the translator is known to be a solvable problem. Determining the proper mapping of Python semantics to Parrot is the research problem. The overwhelming majority of that work is in getting the PMCs right. Not having to worry about the syntax of python or the conversion to bytecodes allows one to focus on just that aspect of the problem.
But, as with all open source projects, feel free to scratch your own itches.
Looks like I'll start with a translator and some new test cases so they can be contributed copyright free.
There also are a fair amount of python test cases in the parrot repository. parrot/languages/python/*/*.t and t/dynclass/python/*.t.
When I last looked, these were not complete. Undoubtably, there is likely to be some minor regressions as I have not kept up with the latest Parrot changes. If past history is any guide, this is not much of a problem.
- Sam Ruby
