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 it correctly. > > We have no plans to write a version of CherryPy which runs on both 2.x > and 3.x, and even fewer plans to try autogenerating any part of > CherryPy-for-Python-3 from the existing code, despite all the hard work > on the 2to3 project. It's all going to be ported to Python 3 by hand to > ensure our invariants are maintained. Therefore, rearranging any modules > from 2.5 to 2.6 just makes more work for our team in the short term > (lots of sys.version checking since we're still supporting Python 2.3) > with zero gain in the long term. I'd rather just make one static name > change (e.g. from "import Cookie" to "import cookie.server") in the new > cp-python-3 branch and be done.
Well, any rearrangement would still work in 2.6, just with a PendingDeprecationWarning. So no sys.version check would be needed to keep things running. -Brett _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
