Re: [Jython-dev] web.py and Jython

[Henrik E. <hen...@gm...>]

That's excellent news. I was beginning to fear that modjy was dead.
I'll make sure to get the bugfixes to you asap (meaning sometime this
week... busy here too...).

'H

On 1/14/07, Alan Kennedy <jyt...@xh...> wrote:
> [Henrik Eriksson]
>  > Does anyone know the status of modjy? I tried sending an email to the
>  > creator (through the web-page), but I haven't gotten any response.
>
> Hi Henrik,
>
> Sorry for the delay in getting back to you; it's been a busy few months;
> new job, new home, New Year, etc.
>
> Thanks for your work with modjy: what you're working on is exactly what
> I always intended for modjy, which is to be a fully compliant WSGI
> server under which popular apps such as Django, Turbogears, etc, can be
> run. I'm delighted to hear that you got CherryPy running.
>
> I'd be happy to hear about any bugs you've found: I will fix them and
> make an updated version available. If you have patches, I'd be happy to
> receive them.
>
> Modjy started as a vehicle for me to understand and participate in
> WSGI's formation. Being a jython advocate, it was only natural that I
> developed my WSGI prototype for jython. Now that it's 95% of the way to
> being complete, I certainly intend to go the last mile.
>
> My plans for modjy are
>
> Near term
> ---------
>
> Fix any and all bugs that are identified, in code or documentation, and
> make new releases.
>
> Medium term
> -----------
>
> 1. Produce a 1.0 release, which will include
>    - A complete test suite. I have a 50% complete test suite written,
> using MockRunner.
>    - Support for bulk file transfers, which uses java.nio if available.
>    - Cleaner support for 2.2 and 2.3 (which will no longer need iterator
> emulation, for example).
>    - Improved J2EE resource loading (no more modjy_jar.location).
>    - Improved importing.
>
> 2. Create a TRAC instance for modjy, i.e. bug tracker, wiki, source code
> browser, etc.
>
> Long term
> ---------
>
> Translate modjy to pure java, which would likely provide performance
> improvements. However, I expect that there's been some API changes
> between jython 2.1 and 2.2/2.3 which might force maintenance of a dual
> code base.
>
> On a slightly tangential note, how are the 2.2 and 2.3 branches coming
> along? I haven't been reading the list for a couple of months, except
> for a cursory glance over some of the more interesting threads. I can
> see a lot's being going on, all of it positive. Is there a summary page
> where I can see current status of the latest versions?
>
> Regards,
>
> Alan.
>
>
>