[Python-Dev] Any PEP about 2.6 -> 3000 code transition?
musiccomposition at gmail.com
Mon Jul 21 20:50:44 CEST 2008
On Mon, Jul 21, 2008 at 1:16 PM, Brett Cannon <brett at python.org> wrote:
> On Mon, Jul 21, 2008 at 2:34 AM, Jesus Cea <jcea at jcea.es> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > Georg Brandl wrote:
> > | So it's good that nobody has written a migration guide yet; he'd have
> > | to rewrite it daily.
> > Yes. I was delaying battling the 3.0 bsddb migration until RC to avoid
> > redoing the same work 15 times XDDDDDDDDDD
> But waiting until all the betas have gone out totally defeats the
> purpose of the betas! It has already been stated that new code changes
> that are even remotely shaky or anything not small needs a code review
> at this point since we only have one beta left. Barry can correct me
> if I am wrong, but dropping a major rewrite of bsddb into 3.0 between
> b3 and rc1 is not acceptable. I wouldn't be surprised if all code
> after b3 requires a code review since at that point we should just be
> squashing bugs, not rewriting code. And if you are migrating all of
> bsddb3 at once then that is going to be a massive code review that
> should be happening in prep for rc1.
I have a sickening feeling that this isn't the only major change that may
hit the betas. PEP 3118 is only about 2/3's implemented (with hardly any
tests, I might add), and Travis has said the earliest he can get to it is
"There's no place like 127.0.0.1."
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev