On Feb 5, 2008 3:40 PM, Robert Brewer <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
> > So my question is whether you all would be up for handling a merging
> > of Cookie and cookielib for 2.6?
>
> I appreciate the thought and effort for a smooth transition, but -1 on
> this idea if I understand
Brett Cannon wrote:
> Since Bill Janssen prodded me on to this list I might as well take
> advantage now and bug you all about how to deal with Cookie and
> cookielib in the stdlib reorg.
>
> My current idea is the new names cookie.client and cookie.server for
> Cookie and cookielib, respectively.
Brett Cannon wrote:
> So my question is whether you all would be up for handling a merging
> of Cookie and cookielib for 2.6?
I appreciate the thought and effort for a smooth transition, but -1 on
this idea if I understand it correctly.
We have no plans to write a version of CherryPy which runs o
Since Bill Janssen prodded me on to this list I might as well take
advantage now and bug you all about how to deal with Cookie and
cookielib in the stdlib reorg.
My current idea is the new names cookie.client and cookie.server for
Cookie and cookielib, respectively. While this goes against the goa
> I think most web frameworks use setuptools at this point. I'd rather
> get this as a distribution, rather than from the standard library. In
> fact, I'd prefer to see all web-development libraries distributed
> separate from the language in Python 3.
Keep in mind that there are two users of th
