Re: [Python-Dev] Python on non IEEE-754 platforms: plea for information.
Mark Dickinson wrote: > Thank you: a very useful thread. From what little information I'm turning > up on Google, it looks as though most of these devices---if they support > floating-point at all---provide some reasonably close approximation to IEEE > 754 floats (possibly emulated in software). Some of the devices have a (slow) floating point engine. But it's sometimes disabled to safe power or userland software can't sometimes access the FPU. Some devices can (ab)use the DSP or GPU/OpenGL engine to speed up floating point ops. Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] A word of warning against using sqlite3 from MacPorts
I was running the test suite today and I was getting a segfault in test_sqlite. That seemed odd since I had not seen any issues on any buildbots. And running the test independently was fine. Noticing that sqlite 3.5.5 was recently available I had MacPorts update. Unfortunately this didn't fix things. I narrowed things down to running test_ctypes before test_sqlite as the trigger. In order to debug I wanted to use a version of sqlite that I had compiled. So after figuring out which package to download (turned out to be the amalgamation version with shell.c and the included makefile), and discovering a bug in setup.py where directories from CPPFLAGS were being searched in reversed from their declared order, I managed to get a build with my own version and the problem went away. So I suspect that sqlite3 from MacPorts is built in such a way as to cause issues. This on Leopard which might also somehow influence things. -Brett ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Any tips to tell sprinter at PyCon about developing on Windows?
This year at PyCon, sprint coaches are giving tutorials up to three hours long the night before sprinting starts. Being the sprint coach on the core means that I get to be that person for the core. Here is to hoping people wait for me for dinner that night. Anyway, to make the tutorial as useful as possible I need to worry about Windows users. But being an OS X/UNIX user, I don't know how to help these people. =) As or right now I am going to point them to the readme.txt file in PCbuild for build instructions. But I don't know if there is any tips or tricks I should be pointing out to them in terms of developing on Python. I mean I assume they can use the build executable from their svn checkout and have it pick up changes they make to code in the checkout, right? I honestly don't know how different it is to develop on Windows than on UNIX. So any info that people can give me to cover would be helpful. -Brett ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Any tips to tell sprinter at PyCon about developing on Windows?
Brett Cannon wrote: > Anyway, to make the tutorial as useful as possible I need to worry > about Windows users. But being an OS X/UNIX user, I don't know how to > help these people. =) As or right now I am going to point them to the > readme.txt file in PCbuild for build instructions. But I don't know if > there is any tips or tricks I should be pointing out to them in terms > of developing on Python. I mean I assume they can use the build > executable from their svn checkout and have it pick up changes they > make to code in the checkout, right? I honestly don't know how > different it is to develop on Windows than on UNIX. > > So any info that people can give me to cover would be helpful. I can provide some guidance for the poor Windows souls. :] The VS 2008 Express Edition makes it easy to compile Python on Windows. There is no need to install any extra SDK packages, additional compilers or whatsoever. Windows users need: Visual Studio Express Edition (VS C++ 2008) http://www.microsoft.com/express/ Tortoise SVN (integrates into the explorer) http://tortoisesvn.net/ Putty for writable checkouts (I highly recommend to use the agent) http://www.chiark.greenend.org.uk/~sgtatham/putty/ Not required but very useful Notepad++ to edit Python files http://notepad-plus.sourceforge.net/ Total Commander (best Norton Commander clone for Windows) http://ghisler.com/ SVN command line program http://subversion.tigris.org/project_packages.html Unix for Windows http://cygwin.com/ The PCbuild directory contains several helper bat files. The most important files are build_env.bat and rt.bat. Build_env.bat opens a command prompt and sets several env vars. rt.bat is a wrapper for the unit test suite. I normally use "rt -q" or "rt -q -v test_egg test_spam". build.bat must be run inside build_env command prompt. build_pgo won't work with the express edition. The Windows developers should checkout the sources in a directory without non ASCII chars and without spaces. I'm using the directory c:\dev\python\ as root for development on Windows. Checkout the trunk and py3k in the directory as well as the external dependencies. You don't need Perl for the ssl package but Express Edition users must compile BSDDB manually for Win32 Release|db_static and Win32 Debug|db_static. build_tkinter.py builds the Tkinter dependencies. I'm trying to hang out on IRC during PyCon so I might be able to assist with Windows questions. It would be really cool if you can recruit some experienced Windows developers. :] Christian ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Should a change in search order of directories in setup.py be backported?
I found out that the directories listed in $CPPFLAGS and $LDFLAGS were being added in reverse order in setup.py. That meant having ``-I/foo -I/bar`` was searching /bar first. I fixed setup.py in the trunk so that the declared order if followed instead. But should this be backported? It will change how extensions are compiled if there is more than one version on a machine. Not sure if we want people to suddenly have what they link against change in a micro release. -Brett ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Should a change in search order of directories in setup.py be backported?
Brett> [fix setup.py search order] Brett> But should this be backported? +1. Seems like a bug to me. Skip ___ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
