<br><div><span class="gmail_quote">On 2/26/08, <b class="gmail_sendername">Brett Cannon</b> <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Feb 26, 2008 at 1:52 PM, Facundo Batista<br> <<a href="mailto:facundobatista@gmail.com">facundobatista@gmail.com</a>> wrote:<br> > 2008/2/26, "Martin v. Löwis" <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>>:<br>
><br> ><br> > > They check out bsddb from subversion, see Tools/buildbot/external.<br> > > If you don't trust that they did so correctly, edit the script to<br> > > remove bsddb, check that in, wait for them to delete it, then revert<br>
> > the script, check in again, and see how they build it.<br> ><br> > No, I wasn't aware of this mechanisms at all. I don't even know how to<br> > build Python in a Windows...<br> ><br> > Anyway, I don't think it's a bad checkout or something, as the same<br>
> error happens in two different machines.<br> ><br> > I don't know, :(<br> <br>Or we can get rid of bsddb and not have the problem anymore. =)<br> <br> -Brett</blockquote><div><br>-1<br><br>Using that logic I prefer just getting rid of Windows to stop having these problems. That'd solve the ssl applink issue and msi installer building issue as well. =P<br>
<br>My opinion on bsddb as a standard library module is based mostly on "its always been there" and a vague memory of the last time this came up I thought people piped up saying they liked batteries being included, including bsddb and sqlite, but I don't have a handy reference to that email thread.<br>
</div><br>-gps<br></div><br>