I ran bootstrap.py every time, so I don't think that was the issue. I can
say with some confidence that installing pyjamas from the zip file and not
from the git clone fixed the problem I was experiencing that caused the
timerdemo example to fail under pyjd.

C. Anthony: Your comment about eliminating pyjd has me a bit worried...
Are you eliminating pyjd and replacing it with a similar capability or just
eliminating it?
The ability to test on the desktop before compiling to javascript is a key
feature of pyjamas from my perspective.
Eliminating that capability would be a real loss, for me at least.
Thoughts?
I guess I'm a fairly "imperfect" developer so the ability to quickly see if
I "fxxxed up" by testing under pyjd first before compiling to javascript is
really important.
If pyjd goes altogether, I may have to bite the bullet and code directly in
javascript and leave pyjamas altogether.  That would be sad.


On Thu, Nov 1, 2012 at 1:47 PM, C Anthony Risinger <[email protected]> wrote:

> On Thu, Nov 1, 2012 at 8:45 AM, Vsevolod Fedorov
> <[email protected]> wrote:
> > On 11/01/12 16:09, Eric Rosenbloom wrote:
> >>
> >>
> >> Anyone have a clue as why most of the files would be missing from the
> pyjd
> >> folder when pulling pyjamas using git?
> >
> >
> > May be I can clarify this.
> > If I am not mistaken, pyjd/__init__.py is generated from pyjd/__init__.
> py.in
> > when you run:
> >
> > python bootstrap.py
> >
> > You must run it every time you:
> > 1. check out / clone repository
> > 2. pull from repository
> > 3. checkout some other revision
> >
> > But, of course, this may be too obvious reason, and there is some
> another. I
> > am not actually a pyjs expert.
>
> nah, you are correct -- it's generated unnecessarily, and i'll be
> eliminating the need soon (along with the entire pyjd module), but
> running bootstrap after a checkout is a good rule of thumb.
>
> this file rarely changes, but in the last few months it was updated
> several times as i reworked the initialization process.
>
> --
>
> C Anthony
>
> --
>
>
>
>

-- 



Reply via email to