At first I was going to respond "+1". But the fact that a couple of
years haven't led to much suggests that it's unlikely to be fruitful;
there just are too many diverging ideas on what is right. (Which makes
sense since it's a huge and fast developing field.)
So unless someone (Alan Kennedy?) act
Guido van Rossum wrote:
> At first I was going to respond "+1". But the fact that a couple of
> years haven't led to much suggests that it's unlikely to be fruitful;
> there just are too many diverging ideas on what is right. (Which makes
> sense since it's a huge and fast developing field.)
>
> S
> What would we be PEPing?
Well, when we started, I made up a list of various things that seem to
be missing in the standard library, like server-side support for
SSL-encrypted socket connections.
http://www.parc.com/janssen/web-sig/needed.html
Bill
__
Alan Kennedy wrote:
> Thinking about this some more, it's beginning to sound to me like the
> server-side web support in the standard library needs a proper review
> and possible rework: it's slowly decohering/kipplizing.
>
> Maybe we need a PEP, so that we can all discuss the subject
> (rationall
On 2/16/06, Alan Kennedy <[EMAIL PROTECTED]> wrote:
> [Ian Bicking]
> > Anyway, I'm +1 on the object [wsgiref's wsgi header manipulation class]
> > going somewhere. I don't know if the
> > parent package has to be named "wsgi" -- and "wsgiref" seems even
> > stranger to me, as anything in the stan
> - CSS Parser
>
>I think John Lee has done some work on this? Beats me. I've never
> felt any need for CSS parsing personally.
>
If you are doing any work with the Web (spidering, for instance), and
need to do rendering of the Web pages (say, for pop-out prism, or
building an ebook from
Hi,
In the same goal as wsgiserver, what do you think to add two middleware
to can really make quickly a meta-framework and "play" immediatly with
it without any external dependency.
I think about cookies and session.
bye
--
William Dodé - http://flibuste.net
