Updates for everyone

[Christian Iversen]

Hi everybody

Time for a status update!

1) I have reviewed Gordons massive patches to include module support.
They are very good, and they have just been merged as of now! If you'd
like to help test it, please check out my "devel" branch, and try it. If
you find any problems, please let us know here.

On behalf if the entire Pyjaco project, I'd like to thank Gordon for his
hard work on this.

Now, there might still be things we have to make minor adjustments to
before merging into stable, but I think this is a huge step forward for
the project. Especially, I'd like your help, Samuel, in reviewing the
changes to the test core. I briefly skimmed it, but I'm not an expert on
that code, so could you please take a look at it?

2) We have a new member here, Tobias Baum. He's currently lurking, but
might be interested in joining the project. Please welcome him, and make
him feel at home :)

3) We should get moving with the IST compiler. We already have the
design down, we just need to get to the fun part: coding.

I'm pretty low on spare time at the moment, unfortunately, but if
anybody would like to do some IST coding, I can help you get started.
Seriously, at least for me, it's the most fun part of the entire
project, and I wish I could have it all to myself ;-)

Well that's it for now - keep up the good work guys!

--
Med venlig hilsen
Christian Iversen

[Dusty Phillips]

> 3) We should get moving with the IST compiler. We already have the
> design down, we just need to get to the fun part: coding.
>
> I'm pretty low on spare time at the moment, unfortunately, but if
> anybody would like to do some IST coding, I can help you get started.
> Seriously, at least for me, it's the most fun part of the entire
> project, and I wish I could have it all to myself ;-)

I'd like to dive into this, but I'm actually in the negative numbers
when it comes to spare time. Things may slow down in mid-winter.

I'd also like to mention that anyone who wants to contribute to
Christian having more spare time to work on pyjaco might do well to tip
him using gittip:

https://www.gittip.com/github/chrivers/

Cheers,

Dusty

[Dexter]

I'd like to work on it as well, but appearantly lately my spare time is dedicated to entertainment (games).

But I want to pick it up again. But every help/cooperation is welcome. 

How are we going to address coordination? making tickets in github and assigning yourself to it?

I guess we should create a more concrete roadmap than we have right now. 

Greetings, Dexter

--
You are subscribed to the Google Group pyj...@googlegroups.com
To unsubscribe from this group, send email to
pyjaco+unsubscribe@googlegroups.com

[Samuel Ytterbrink]

I will try to look at the pull request. My Github announcement channel have been flooded, so could someone post a link to the test pull request.

Im sorry that i havent got to it earlier, my desire for coing have been needed elsewhere(mainly work). 

2012/9/7 Dexter <a.ess...@gmail.com>

pyjaco+un...@googlegroups.com

--
//Samuel Ytterbrink

[gordon pendleton]

On Fri, Sep 7, 2012 at 10:52 AM, Samuel Ytterbrink <nep...@gmail.com> wrote:

I will try to look at the pull request. My Github announcement channel have been flooded, so could someone post a link to the test pull request.

Im sorry that i havent got to it earlier, my desire for coing have been needed elsewhere(mainly work). 

https://github.com/chrivers/pyjaco/pulls/thenewguy and click the "closed" button.

These were my first pull requests for pyjaco submitted via github so the ones there are the ones in question. 

[gordon pendleton]

https://github.com/chrivers/pyjaco/pulls/thenewguy and click the "closed" button.

These were my first pull requests for pyjaco submitted via github so the ones there are the ones in question. 

The pull requests do not appear to be showing the right branches though.  

[Christian Iversen]

On 2012-09-07 16:43, Dexter wrote:
> I'd like to work on it as well, but appearantly lately my spare time is
> dedicated to entertainment (games).
> But I want to pick it up again. But every help/cooperation is welcome.
>
> How are we going to address coordination? making tickets in github and
> assigning yourself to it?
> I guess we should create a more concrete roadmap than we have right now.

I will address coordination for now. I think ticket on GitHub would be a
good idea once we have the basic tasks split up:

So, the way I see it:

- IST namedtuples
- AST -> IST converter
- IST -> IST semantifier (for __getattr__, etc)
- IST -> JS pretty printer
- IST -> IST tree dump (for debugging)
- Maybe some stdlib adjustments

Now, we absolutely need to start with the first item.

In other words, we need IST namedtuples for all the IST types we need to
process. These are by and large the same types as AST, but of course in
simplified IST form (and not dependent on the AST module at all).

Who's up for giving that a shot?

[TB]

Hi everybody,

I for myself would like to start further investigating the code and also testing the different branches, to get a better feeling for the code. While I'm doing that i will probably do something for the documentation (usage and code). I think this might help to get a larger user base for testing and maybe some interested developers as well.

For the documentation a good thing to have would be a "feature list" , ... so whats supposed to work (Syntax, Built-ins, Imports etc.)
 
It looks like there is liddle time and a lot to do in order to bring the new compiler to life. So, despite the decorator issue, what exactly is problem with current compiler in order to rewrite it completely. And How much efforts  would it take to change the decorator issue for the current compiler? So one can  use JavaScript built-ins via import.  something like "from JS import alert" comes to my mind.

In the minutes of the meeting there was also a todo note I'm not sure if this still has to be discussed:
"Design the IST in detail,  what nodes would be there and what fields must be present to be able to traverse the tree, when finding a node that you don’t understand."

When you started to design the new compiler, have you also discussed source maps for debugging?
I'm not sure but i think this has to be considered in the compiler some how.

TB
 

[Dexter]

Yeah, we discussed sourcemaps.

The idea is that information regarding the original source should be stored in the ist nodes somehow. 

The writer would be responsible for creating the source maps. If the python linenumers are still available, it is able to do that.

--
You are subscribed to the Google Group pyj...@googlegroups.com
To unsubscribe from this group, send email to

pyjaco+un...@googlegroups.com

[Luke Stanley]

Hey all was just thinking of this project, Pyconuk is starting in days.

May I ask, what does IST mean? I know AST means Abstract Syntax Tree.

By the way I mentioned this project here on Light Table (of which I'm a backer): http://www.kickstarter.com/projects/ibdknox/light-table/posts/316589

For some reason they are using Clojure at the moment, it would be awesome to use Pyjaco with Lighttable, as it develops. 

Congrats on the module support!

:)

[Dexter]

Ist stands for intermediate syntax tree, 

It's similar to the AST but we're going to design it. (as the AST doesn't guarantee any stability, at least its prone to changes).

IST will allow us to modify nodes which are pure python constructs (classes, decorators) and transform those into pure javascript constructs. 

How do you mean use pyjaco with lighttable? I've heard lighttable's second language will be python. So you could develop pyjaco in it. 

Greetings, Dexter

--

[Luke Stanley]

On Thursday, 27 September 2012 00:38:33 UTC-7, Dexter wrote:

Ist stands for intermediate syntax tree, 

It's similar to the AST but we're going to design it. (as the AST doesn't guarantee any stability, at least its prone to changes).

IST will allow us to modify nodes which are pure python constructs (classes, decorators) and transform those into pure javascript constructs. 

Ahh I see, thanks for the explanation :) 

 

How do you mean use pyjaco with lighttable? I've heard lighttable's second language will be python. So you could develop pyjaco in it. 

I mean compiling Python to Javascript while using Lighttable, which compiles Clojure to Javascript at present, as it's default language I think. 

I spoke with the Larch environment programmer Geoffrey French at Pyconuk too (which ended on Monday). He has a visual workbook thing he coded with Java and Jython, which I think would be nice to use in the browser. (I was suggesting ShareJS.org may offer useful pointers for such a task.)

Exciting stuff!

[Dexter]

Its certainly exiting stuff. Please keep us updated :).. I would love to find a suited python ide. (currently just using kate + konsole)

[Samuel Ytterbrink]

Im using VIM, think it works ok, i tried to use PyCharm, but it failed to charm me! though I love there PHPStorm (makes PHP livable). Somehow Python is its own IDE, but i recommend bpython for scouting.

2012/10/5 Dexter <a.ess...@gmail.com>

--
//Samuel Ytterbrink