> Removing the dependency on db_static.vcproj and merging the relevant
> source code files into _bsddb.vcproj did the trick -- all x64
> bsddb-related tests now pass. The only issue with this approach is
> that it locks _bsddb.vcproj into 4.4.20. However, considering that
> this approach (i.e. br
> > Removing the dependency on db_static.vcproj and merging the relevant
> > source code files into _bsddb.vcproj did the trick -- all x64
> > bsddb-related tests now pass. The only issue with this approach is
> > that it locks _bsddb.vcproj into 4.4.20. However, considering that
> > this approac
> I reviewed all the compiler options used by db_static.vcproj -- the
> only thing I needed to bring over was -DDIAGNOSTIC for debug builds.
> Everything else either had no impact and could be safely dropped, or
> conflicted with compiler options used by the rest of the python build
> (function lev
ACTIVITY SUMMARY (03/07/08 - 03/14/08)
Tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue
number. Do NOT respond to this message.
1735 open (+23) / 12380 closed (+14) / 14115 total (+37)
Open issues with patches: 474
Average durati
While fixing the broken links in the docs, I saw that the link to
http://www.pythonlabs.com/logos.html in the "BEOPEN PYTHON OPEN SOURCE
LICENSE AGREEMENT VERSION 1" is broken.
What to do about that?
Georg
___
Python-Dev mailing list
Python-Dev@python.
In the keynote, Guido mentioned switching from range to xrange in 2.6
code, as a migration strategy. Another option would be to add range to
future_builtins, and have it call xrange. Would that be desirable?
___
Python-Dev mailing list
Python-Dev@pyth
On Fri, Mar 14, 2008 at 7:24 PM, Georg Brandl <[EMAIL PROTECTED]> wrote:
> While fixing the broken links in the docs, I saw that the link to
> http://www.pythonlabs.com/logos.html in the "BEOPEN PYTHON OPEN SOURCE
> LICENSE AGREEMENT VERSION 1" is broken.
>
> What to do about that?
Too bad. BeO
Sure. The 3.0 range() isn't exactly the same as the 2.6 xrange(), so
it would have to be a proper backport (sorry, I don't recall the exact
difference, but I remember it's been redone, perhaps to support long
integers).
It seems pretty minor though. The advantage of using xrange() is that
you rema
Hi,
I appologize if this is not the right place to post this, but searching
through the old archives, I ran across the same issue from 3 years ago, but
I cannot find the resolution to it.
Currently, I am trying to build the python2.4 SRPM from Python.org on a
CentOS4.6_x64 platform, but the bu
