Re: [Webware-devel] Webware 1.1 and beyond

[Mark P. <mar...@mo...>]

Perhaps the addition of wsgi, disutils, and so on, calls for a v2  
product.

  - Mark

On Jun 12, 2009, at 10:32 AM, Roger Haase <cro...@ya...>  
wrote:

>
>
>
> --- On Fri, 6/12/09, Christoph Zwerschke <ci...@on...> wrote:
>
>> From: Christoph Zwerschke <ci...@on...>
>> Subject: [Webware-devel] Webware 1.1 and beyond
>> To: web...@li...
>> Date: Friday, June 12, 2009, 12:50 AM
>> As already announced, I have created
>> a branch for the Webware for Python
>> 1.0.x bugfix releases.
>>
>> Development in the trunk is now for release 1.1.
>>
>> The idea is to slowly modernize and future-proof Webware
>> for Python.
>>
>> The 1.1 version will be the first step in the process with
>> the main goal
>> of trimming all the old cruft that existed to make Webware
>> backward
>> compatible down to Python 2.0, and use some of the newer
>> Python features
>> to simplify and streamline the code and make it a bit more
>> performant.
>> Things that have already been deprecated will be removed.
>>
>> The trimmed version will make development much less
>> painful.
>>
>> Version 1.2 will then make more creative use of newer
>> Python features.
>> For instance, I can imagine converting some of the getter
>> methods into
>> properties. This means you would then be able to write
>> self.request
>> instead of self.request(). This would be done in a backward
>> compatible
>> way (e.g. by making request callable and returning self).
>> Another idea
>> is to use decorators for actions.
>>
>> Later versions will then tackle more involved things like
>> replacing the
>> Webware plugin and documentation system with something more
>> modern and
>> standard (I'm thinking of Distutils, pip, Sphinx etc.).
>>
>> I think we should also support WSGI. We could then replace
>> mod_webkit
>> with mod_wsgi.
>>
>> In the past I had been sceptical about the future of the
>> ThreadedAppServer because it does not scale on multi-core
>> and
>> multi-processor hardware because of the GIL. So I had
>> already suggested
>> getting rid of it in the long run and simply making Webware
>> a thin WSGI
>> layer, and some were disappointed because of that. But
>> there have been
>> interesting developments in the last time - maybe this will
>> be solved
>> for us with the unladen swallow project and
>> ThreadedAppServer will
>> continue to be useful. So let's postpone that discussion.
>>
>> I will also use the new 1.1 version as an opportunity to
>> break the long
>> Webware tradition of using tabs instead of spaces. The
>> thing is that
>> using 4 spaces has become the most popular style and is
>> recommended in
>> PEP8. It's also used in all the other open source Python
>> projects I'm
>> contributing to; and I always forgot switching my editor
>> for Webware.
>>
>> So from now on:
>>
>> "Thou shalt indent with four spaces. No more, no less. Four
>> shall be the
>> number of spaces thou shalt indent, and the number of thy
>> indenting
>> shall be four. Eight shalt thou not indent, nor either
>> indent thou two,
>> excepting that thou then proceed to four. Tabs are right
>> out."
>>
>> -- Christoph
>>
>
> Thank you for all your effort Christoph,
>
> I consider replacing tabs with spaces and wsgi support 2 giant steps  
> forward.
>
> Roger Haase
>
>
>
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> Webware-devel mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webware-devel