6 ms·

> I am unconvinced and still think the claim is false advertising. A port of Python 3 to Parrot is under active development (with the knowledge of PSF, which w

> I am unconvinced and still think the claim is false advertising. A port of Python 3 to Parrot is under active development (with the knowledge of PSF, which will probably hold the copyright on the project soon). It needs more developers, but what project doesn't? Pynie is also a first-class project. Any changes it needs to run well it will get. (In truth, we test it and a few other high-level languages against Parrot trunk before we release our monthly versions.) If you refuse to believe that Parrot developers are sufficiently serious about achieving our goals and that we work on them with every release, well, that's your prerogative. It would have been nice if you'd looked at our Languages page first, however.

btilly 17y ago
You're criticizing me for not looking at your Languages page, when in fact that page has nothing to say that diminishes any point I've been making. As I already pointed out to you, Python 3 is far from the most widely pointed out version of Python. The actual versions people are use in the wild are the 2.x line. Judging from http://pirate.tangentcode.com/ http://pirate.tangentcode.com/, the unsuccessful attempt to port Python 2 has been abandoned for several years. When it started it was called a first class project as well. There was theoretically lots of visible support. There is lots of prior art on how to successfully port it to a virtual machine. Some really good people tried to make it work. And the failure to port it resulted in literal pie in the face for the lead developer of Parrot. I know that a number of things have improved about the project. Parrot is much healthier than it was. But I can't personally bother caring about it until after I see it succeeding with what should be the relatively easy stuff.
- chromatic 17y ago
  > ... what should be the relatively easy stuff. Volunteer time, interest, ability, and resources aren't fungible. Find us a willing cadre of developers to work on Pynie and I'll accept that writing and maintaining a full Python implementation is indeed "relatively easy".
  - btilly 17y ago
    Well you had Sam Ruby. But then burned him out... If you can get Jim Hugunin involved then I'm sure you'll succeed. Actually you should reach out to him in any case, because he has more direct understanding of experience in making Python work with VMs than anyone else out there. Even if he isn't interested in putting out effort, I'm sure that any pointers he gives you will prove very helpful.

btilly 17y ago

You're criticizing me for not looking at your Languages page, when in fact that page has nothing to say that diminishes any point I've been making. As I already pointed out to you, Python 3 is far from the most widely pointed out version of Python. The actual versions people are use in the wild are the 2.x line. Judging from http://pirate.tangentcode.com/ http://pirate.tangentcode.com/, the unsuccessful attempt to port Python 2 has been abandoned for several years. When it started it was called a first class project as well. There was theoretically lots of visible support. There is lots of prior art on how to successfully port it to a virtual machine. Some really good people tried to make it work. And the failure to port it resulted in literal pie in the face for the lead developer of Parrot. I know that a number of things have improved about the project. Parrot is much healthier than it was. But I can't personally bother caring about it until after I see it succeeding with what should be the relatively easy stuff.

chromatic 17y ago
> ... what should be the relatively easy stuff. Volunteer time, interest, ability, and resources aren't fungible. Find us a willing cadre of developers to work on Pynie and I'll accept that writing and maintaining a full Python implementation is indeed "relatively easy".
- btilly 17y ago
  Well you had Sam Ruby. But then burned him out... If you can get Jim Hugunin involved then I'm sure you'll succeed. Actually you should reach out to him in any case, because he has more direct understanding of experience in making Python work with VMs than anyone else out there. Even if he isn't interested in putting out effort, I'm sure that any pointers he gives you will prove very helpful.