On Thu, Feb 28, 2008 at 5:31 PM, Robert Brewer <[EMAIL PROTECTED]> wrote:
> I'd propose:
>
> Cookie -> http.cookies
> cookielib -> http.cookiejar
On Thu, Feb 28, 2008 at 8:46 PM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> +1 from me.
And +1 from me as well.
-Fred
--
Fred L. Drake, Jr.
On Thu, Feb 28, 2008 at 5:31 PM, Robert Brewer <[EMAIL PROTECTED]> wrote:
> Brett Cannon wrote:
> > So my question is what do people see as a possible naming scheme for
> > these modules? Cookie has to be renamed because of its PEP 8
> > violation. Here are some ideas::
> >
> > cookielib ->
Brett Cannon wrote:
> So my question is what do people see as a possible naming scheme for
> these modules? Cookie has to be renamed because of its PEP 8
> violation. Here are some ideas::
>
> cookielib -> cookielib
> Cookie -> cookielib2 (with plans to move what needs to go from Cookie
> into
When I brought this up last it was when I first began bombarding this
list with stdlib reorganization questions, so there was some noise
about the whole process and no clear resolution was reached.
The problem is that both modules have a Cookie class, so they can be
merged. Much like the url* issu
