Simon Burton [EMAIL PROTECTED] wrote:
Is there a python interface ?
Not yet.
Neil
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
On Tue, Oct 25, 2005 at 01:36:26PM +1000, Simon Burton wrote:
Is there a python interface ?
Not yet, as far as I know.
FYI, all: please see the following weblog entry for a description of
the AST branch:
http://www.amk.ca/diary/2005/10/the_ast_branch_lands_1
If I got anything wrong,
On 10/20/05, Neal Norwitz [EMAIL PROTECTED] wrote:
The Grammar is (was at one point at least) shared between Jython andwould allow more tools to be able to share infrastructure.The ideais to eventually be able to have [JP]ython output the same AST totools.
Hello Python-dev,
My name is Frank
On 10/25/05, Frank Wierzbicki [EMAIL PROTECTED] wrote:
My name is Frank Wierzbicki and I'm working on the Jython project. Does
anyone on this list know more about the history of this Grammar sharing
between the two projects? I've heard about some Grammar sharing between
Jython and Python,
Guido van Rossum wrote:
On 10/25/05, Frank Wierzbicki [EMAIL PROTECTED] wrote:
My name is Frank Wierzbicki and I'm working on the Jython project. Does
anyone on this list know more about the history of this Grammar sharing
between the two projects? I've heard about some Grammar sharing
On 10/25/05, Samuele Pedroni [EMAIL PROTECTED] wrote:
Your best bet is to track down Jim Hugunin and see if he remembers.
He's jimhug at microsoft.com or jim at hugunin.net.
no. this is all after Jim, its indeed a derived effort from the CPython
own AST effort, just that we started using it
On Fri, 21 Oct 2005 18:32:22 + (UTC)
nas at arctrix.com (Neil Schemenauer) wrote:
Does it just allow us to do new and interesting manipulations of
the code during compilation?
Well, that's a pretty big deal, IMHO. For example, adding
pychecker-like functionality should be straight
Anthony Baxter wrote:
So it looks like the AST branch has landed. Wooo! Well done to all who
were involved - it seems like it's been a huge amount of work.
Congratulations from this quarter, too.
I really liked the structure of the new compiler in the limited time I spent
working with it on
On 10/20/05, Neal Norwitz [EMAIL PROTECTED] wrote:
On 10/20/05, Anthony Baxter [EMAIL PROTECTED] wrote:
Could someone involved give a short email laying out what concrete (no
pun intended) advantages this new compiler gives us? Does it just
allow us to do new and interesting manipulations
On 10/20/05, Guido van Rossum [EMAIL PROTECTED] wrote:
On 10/20/05, Anthony Baxter [EMAIL PROTECTED] wrote:
So it looks like the AST branch has landed. Wooo! Well done to all who
were involved - it seems like it's been a huge amount of work.
Hear, hear. Great news! Thanks to Jeremy, Neil
Anthony Baxter [EMAIL PROTECTED] wrote:
Could someone involved give a short email laying out what concrete (no
pun intended) advantages this new compiler gives us?
One advantage is that it decreases the coupling between the parser
and the backend of the compiler. For example, it should be
On 10/21/05, Neil Schemenauer [EMAIL PROTECTED] wrote:
Also, the concrete syntax tree (CST) generated by Python's parser is
not a convenient data structure to deal with. Anyone who's used the
'parser' module probably experienced the pain:
parser.ast2list(parser.suite('a = 1'))
[257,
I'm still making slow progress on this front. I have a versioned
merged to the CVS head. I'd like to make a final pass over the patch.
I'd upload it to SF, but I can't connect to a web server there. If
anyone would like to eyeball that patch before I commit it, I can
email it to you.
Jeremy
Hi Jeremy,
On Thu, Oct 13, 2005 at 04:52:14PM -0400, Jeremy Hylton wrote:
I don't think the current test suite covers all of the possible syntax
errors that can be raised. I'd like to add a new test suite that
covers all of the remaining cases, perhaps moving some existing tests
into this
I just merged the head back to the AST branch for what I hope is the
last time. I plan to merge the branch to the head on Sunday evening.
I'd appreciate it if folks could hold off on making changes on the
trunk until that merge happens.
If this is a non-trivial inconvenience for anyone, go
[Jeremy]
Neil and I have been working on the AST branch for the last week.
We're nearly ready to merge the changes to the head.
[Raymond]
Nice work.
Indeed. I should've threatened to kill the AST branch long ago! :)
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
On 10/13/05, Guido van Rossum [EMAIL PROTECTED] wrote:
Indeed. I should've threatened to kill the AST branch long ago! :)
:-)
I decreased a lot of the memory leaks. Here are some more to work on.
I doubt this list is complete, but it's a start:
PyObject_Malloc (obmalloc.c:717)
On 10/14/05, Neal Norwitz [EMAIL PROTECTED] wrote:
I decreased a lot of the memory leaks. Here are some more to work on.
I doubt this list is complete, but it's a start:
Oh and since I fixed the memory leaks in a generated file
Python/Python-ast.c, the changes still need to be implemented in
Neil and I have been working on the AST branch for the last week.
We're nearly ready to merge the changes to the head. I imagine we'll
do it this weekend, barring last minute glitches.
There are a few open issues that remain. I'd like to merge the branch
before resolving them. Please let me
I'm excited to see work continuing (resuming?) on the AST tree.
I don't know how many machines you've been able to test the AST branch on. I
have a linux/amd64 machine handy and I've tried to run the test suite with a
fresh copy of the ast-branch.
test_trace segfaults consistently, even when
On Thu, Oct 13, 2005 at 05:08:41PM -0500, [EMAIL PROTECTED] wrote:
test_trace segfaults consistently, even when run alone.
That's a bug in frame_setlineno(), IMO. It's failing to detect an
invalid jump because the lnotab generated by the new compiler is
slightly different (DUP_TOP opcode
On Fri, Oct 14, 2005 at 01:03:28AM -0400, Raymond Hettinger wrote:
Do the AST branch generate a syntax error for:
foo(a = i for i in range(10))
No. It generates the same broken code as the current compiler.
Neil
___
Python-Dev mailing list
Nick Coghlan wrote:
Brett C. wrote:
I noticed Nick's PEP is still not
up. Probably too busy with that fix for genexps in the AST branch, huh,
Nick? =)
Something like that. . . still, I finally got around to fixing the formatting
in
the text file and sending it back to David :)
Add to
Nick Coghlan wrote:
Nick Coghlan wrote:
Brett C. wrote:
I noticed Nick's PEP is still not
up. Probably too busy with that fix for genexps in the AST branch, huh,
Nick? =)
Something like that. . . still, I finally got around to fixing the formatting
in
the text file and sending it back
I think it would be easier to create a new branch from the current
head, integrate the small number of changed files from ast-branch, and
work with that branch instead. The idea is that it's an end-run
around doing an automatic CVS merge and relying on someone to manually
merge the changes.
25 matches
Mail list logo
