<div dir="ltr"><br><br><div class="gmail_quote">On Mon, Jul 21, 2008 at 1:16 PM, Brett Cannon <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, Jul 21, 2008 at 2:34 AM, Jesus Cea <<a href="mailto:jcea@jcea.es">jcea@jcea.es</a>> wrote:<br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> Georg Brandl wrote:<br>
> | So it's good that nobody has written a migration guide yet; he'd have<br>
> | to rewrite it daily.<br>
><br>
> Yes. I was delaying battling the 3.0 bsddb migration until RC to avoid<br>
> redoing the same work 15 times XDDDDDDDDDD<br>
><br>
<br>
</div>But waiting until all the betas have gone out totally defeats the<br>
purpose of the betas! It has already been stated that new code changes<br>
that are even remotely shaky or anything not small needs a code review<br>
at this point since we only have one beta left. Barry can correct me<br>
if I am wrong, but dropping a major rewrite of bsddb into 3.0 between<br>
b3 and rc1 is not acceptable. I wouldn't be surprised if all code<br>
after b3 requires a code review since at that point we should just be<br>
squashing bugs, not rewriting code. And if you are migrating all of<br>
bsddb3 at once then that is going to be a massive code review that<br>
should be happening in prep for rc1.</blockquote><div><br>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 August... <br>
</div></div><br><br clear="all"><br>-- <br>Cheers,<br>Benjamin Peterson<br>"There's no place like <a href="http://127.0.0.1">127.0.0.1</a>."
</div>