What is "PAST"?

[Sam Ruby]

Please forgive the newbie question, but I am trying to see if I can
assess the current state of Python on Parrot to see if I can help in any
way.

I've jotted down some of what I have found so far here:

http://www.intertwingly.net/blog/2004/10/02/Pyrate

- Sam Ruby

[Leopold Toetsch]

> http://www.intertwingly.net/blog/2004/10/02/Pyrate

Nice summary. Some remearks:

- I've started the AST interface, the "unimplemented" is not quite true.
Just compiling an AST string isn't supported. But compiling an AST
source file (e.g. ast/hello.past) basically works.
- Its currently stalled, only a few AST nodes are handled.
- A pure Python or C Python lexer/parser/AST generator will be needed
finally.
- Some Python PMCs will be needed. Scalars and aggregates are simple and
a lot of functionality is already there. It just needs basically
moving existing code pieces around.
- Python metaclass/class/object PMCs are still challenging
- Needs a lot more tests. Is there a low-level Python test suite around
that is able to "bootstrap" the unit-tests?

Any help is very welcome.

> - Sam Ruby

leo

[Sam Ruby]

Leopold Toetsch wrote:

> - I've started the AST interface, the "unimplemented" is not quite true.
> Just compiling an AST string isn't supported. But compiling an AST
> source file (e.g. ast/hello.past) basically works.

What command does one use to compile ast/hello.past?

> - Needs a lot more tests. Is there a low-level Python test suite around
> that is able to "bootstrap" the unit-tests?

I'd like to use the following tests to guide development:

http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Lib/test/

> Any help is very welcome.

First step is to sort through the debris in order to identify what
codebase is most likely to attract a sustainable community of developers.

- Sam Ruby

[Leopold Toetsch]

Sam Ruby wrote:
> Leopold Toetsch wrote:
>
>> - I've started the AST interface, the "unimplemented" is not quite true.
>> Just compiling an AST string isn't supported. But compiling an AST
>> source file (e.g. ast/hello.past) basically works.
>
>
> What command does one use to compile ast/hello.past?

$ ./parrot ast/hello.past
Hello PAST

>
>> - Needs a lot more tests. Is there a low-level Python test suite around
>> that is able to "bootstrap" the unit-tests?
>
>
> I'd like to use the following tests to guide development:
>
> http://cvs.sourceforge.net/viewcvs.py/python/python/dist/src/Lib/test/

Yes, finally. But for the beginning we need low-level tests.

> First step is to sort through the debris in order to identify what
> codebase is most likely to attract a sustainable community of developers.

Yep.

> - Sam Ruby

leo