Re: [Python-Dev] Windows x64 bsddb 4.4.20 woes
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. bringing their source files into our build instead of linking against a static lib compiled with wildly incompatible flags) only took me about two minutes to implement and immediately fixed every bsddb problem I was encoutering, I'm convinced it's the right way to go. (I can separate the dependencies easily enough.) I'm convinced this is the wrong approach. Are you sure you copied all compiler settings over to the project correctly? What is the procedure to upgrade such a setup? What is the procedure for people who want to build with a different version of bsddb? Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Windows x64 bsddb 4.4.20 woes
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. bringing their source files into our build instead of linking against a static lib compiled with wildly incompatible flags) only took me about two minutes to implement and immediately fixed every bsddb problem I was encoutering, I'm convinced it's the right way to go. (I can separate the dependencies easily enough.) I'm convinced this is the wrong approach. Are you sure you copied all compiler settings over to the project correctly? What is the procedure to upgrade such a setup? What is the procedure for people who want to build with a different version of bsddb? 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 level linking, buffer overflow checks, etc). Regarding support for users who want to build with different versions of bsddb; if they want a functional build that passes tests they're going to have to do something similar to the work I've done anyway. As it stands now, the .lib generated by db_static.vcproj for x64 builds just straight out does not work. That can be fixed in two ways: coerce db_static.vcproj into matching our build, or mimicking db_static in a new .vcproj that's contained with our build, inheriting our property sheets. I chose the latter. Trent. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Windows x64 bsddb 4.4.20 woes
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 level linking, buffer overflow checks, etc). If you take out those options from the db_static project, it *should* work just the same as what you've got now, right? Can you use that approach to determine the culprit for making the static library approach fail? As it stands now, the .lib generated by db_static.vcproj for x64 builds just straight out does not work. That can be fixed in two ways: coerce db_static.vcproj into matching our build, or mimicking db_static in a new .vcproj that's contained with our build, inheriting our property sheets. I chose the latter. I would *really* prefer the former. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Summary of Tracker Issues
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 duration of open issues: 739 days. Median duration of open issues: 1152 days. Open Issues Breakdown open 1711 (+23) pending24 ( +0) Issues Created Or Reopened (37) ___ continue documentation 03/07/08 CLOSED http://bugs.python.org/issue2252created blp continue documentation internally inconsistent 03/07/08 CLOSED http://bugs.python.org/issue2253created blp Python CGIHTTPServer information disclosure 03/07/08 http://bugs.python.org/issue2254created m.sucajtys patch Change Mandrake by Mandriva for platform.dist() 03/07/08 CLOSED http://bugs.python.org/issue2255created neoclust patch Install failure of 2.6a1 on Windows XP without VS8 installed 03/07/08 http://bugs.python.org/issue2256created jkleckner typo in tutorial section 4.4 - final break statement is missing 03/08/08 CLOSED http://bugs.python.org/issue2257created Kyte999 Update command line docs for issue 1739468 03/09/08 http://bugs.python.org/issue2258created ncoghlan easy Poor support other than 44.1khz, 16bit audio files? 03/09/08 http://bugs.python.org/issue2259created loki_dePlume patch conditional jump to a POP_TOP optimization 03/09/08 http://bugs.python.org/issue2260created _doublep patch Warning: could not send message for past 4 hours 03/09/08 CLOSED http://bugs.python.org/issue2261created barnabas79 Helping the compiler avoid memory references in PyEval_EvalFrame 03/09/08 http://bugs.python.org/issue2262created jyasskin patch, patch struct.pack() + numpy int raises SystemError 03/10/08 http://bugs.python.org/issue2263created jvr empty specifier for float.__format__ does not always print at le 03/10/08 http://bugs.python.org/issue2264created eric.smith A line in the second example of 7.3.5 Examples in Python Libr 03/10/08 CLOSED http://bugs.python.org/issue2265created furutaka Missing documentation about old/new-style classes03/10/08 http://bugs.python.org/issue2266created Yinon datetime.datetime operator methods are not subclass-friendly 03/10/08 CLOSED http://bugs.python.org/issue2267created stingray patch Fold slice constants 03/10/08 http://bugs.python.org/issue2268created belopolsky patch Problem reporting non-keyword arg after keyword arg syntax error 03/10/08 CLOSED http://bugs.python.org/issue2269created ijmorlan Typo on 8.6.2.5 Document Objects page03/10/08 CLOSED http://bugs.python.org/issue2270created throw6617 msi installs to the incorrect location (C drive)
[Python-Dev] Link in license broken
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.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] range in future_builtins?
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@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Link in license broken
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. BeOpen doesn't exist any more. We can't very well retroactively change their license; they were stupid to put a web link in a license (and if only that was their only stupidity :-). I think having it be a 404 forever is probably the right solution. I have no idea which logos were once there, ane neither does the wayback machine at archive.org... -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] range in future_builtins?
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 remain backwards compatible all the way to 2.0 and probably even 1.5.2... On Fri, Mar 14, 2008 at 8:14 PM, Eric Smith [EMAIL PROTECTED] wrote: 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? -- --Guido van Rossum (home page: http://www.python.org/~guido/) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Problems building python2.4 SRPM on RHEL4 x64
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 build is failing with a very non-descript error message. + cd /var/tmp/python2.4-2.4-root/usr/bin + mv -f pydoc pydoc2.4 + cd /var/tmp/python2.4-2.4-root/usr/bin + mv -f idle idle2.4 + echo '#!/bin/bash' + echo 'exec /usr/bin/python2.4 /usr/lib64/python2.4/idlelib/idle.py' + chmod 755 /var/tmp/python2.4-2.4-root/usr/bin/idle2.4 + cp -a Tools /var/tmp/python2.4-2.4-root/usr/lib64/python2.4 + rm -f mainpkg.files + find /var/tmp/python2.4-2.4-root/usr/lib64/python2.4/lib-dynload -type f + sed 's|^/var/tmp/python2.4-2.4-root|/|' + grep -v -e '_tkinter.so$' error: Bad exit status from /var/tmp/rpm-tmp.55639 (%install) RPM build errors: user jafo does not exist - using root group jafo does not exist - using root user jafo does not exist - using root group jafo does not exist - using root Bad exit status from /var/tmp/rpm-tmp.55639 (%install) The old post I found about this can be found here: http://mail.python.org/pipermail/python-bugs-list/2005-October/030670.html I checked the var/tmp/python2.4-2.4-root/usr/lib64 directories and see plenty of files in there, but not sure what I should be looking for. Can anyone point me in the right direction? Am not sure what to be looking for in order to get this to work. Thanks! Eric ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
