gmane.comp.lang.jython.user

Re: Controlling .$py.class compiling

On Wed, Aug 20, 2008 at 1:25 PM, Leo Soto M. <leo.soto <at> gmail.com> wrote:

How about pre-compiling all your.py files to $py.class before
installing on the production environment? Would that work?

That's my Plan B. Doing that means I have to move more files over to production (both the .py and the $py.class files). And, if the JRE changes, would those files get recompiled again? If so, then they would change and I would have the same problems I just talked about.

--
Mike Hostetler
http://mike.hostetlerhome.com/

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Jython-users mailing list
Jython-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jython-users

headers

Nicholas Riley | 21 Aug 02:34

Re: Controlling .$py.class compiling

In article 
<c60e627c0808201301hdd84606sdf02e460159dad93 <at> mail.gmail.com>,
 "Mike Hostetler" <hostetlerm <at> gmail.com> wrote:

> That's my Plan B. Doing that means I have to move more files over to
> production (both the .py and the $py.class files).  And, if the JRE changes,
> would those files get recompiled again?  If so, then they would change and I
> would have the same problems I just talked about.

No, they only change (for now) between versions of Jython.
--

-- 
Nicholas Riley <njriley <at> uiuc.edu>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

headers

Leo Soto M. | 21 Aug 03:48

Re: Controlling .$py.class compiling

On Wed, Aug 20, 2008 at 4:01 PM, Mike Hostetler <hostetlerm <at> gmail.com> wrote:
>
> On Wed, Aug 20, 2008 at 1:25 PM, Leo Soto M. <leo.soto <at> gmail.com> wrote:
>>
>> How about pre-compiling all your.py files to $py.class before
>> installing on the production environment? Would that work?
>
> That's my Plan B. Doing that means I have to move more files over to
> production (both the .py and the $py.class files).

You can also include only the $py.class files, except for scripts you
want to directly execute. That is, jython foo$py.class won't work, but
"import foo" will work with the foo$py.class file alone.

--

-- 
Leo Soto M.
http://blog.leosoto.com

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/