On Sun, Dec 14, 2008 at 10:55 AM, Darren Dale <dsd...@gm...> wrote: > On Sun, Dec 14, 2008 at 1:28 PM, Michael Abshoff <mab...@go...> > wrote: >> On Sun, Dec 14, 2008 at 10:22 AM, Darren Dale <dsd...@gm...> wrote: >> > On Sun, Dec 14, 2008 at 12:24 PM, Charlie Moad <cw...@gm...> wrote: Hi, <SNIP> >> The express edition can only produce 32 bit binaries, but I guess this >> is better than nothing. > > According to wikipedia > (http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express) : > > "natively compiling 64-bit applications through the IDE is not supported. If > the freely available Windows SDK is installed, 64-bit applications can be > built on the command line using the x64 cross-compiler (Cl.exe) supplied > with the SDK." The documentation at python.org does not indicate whether or > not it is possible to cross-compile with the express edition if the Windows > SDK is installed > (http://docs.python.org/distutils/builtdist.html#cross-compiling-on-windows) Ok, I didn't know that. There is also some movement with the 64 bit MinGW port, so hopefully in 2009 one might see a stable release there, too. >> >> > I the past >> > I have built and distributed extension modules built with mingw32 on >> > windows >> > XP, but I have not been able to put together a working mingw32/msys on a >> > 64-bit windows vista machine. This is my only windows computer, so it >> > looks >> > like I will only be supporting py2.6 in the near future. >> >> Since numpy 1.3 (probably out January 2009) will start supporting >> python 2.6 and official Python 3k support for numpy is currently >> anticipated not for a while I would guess Python 3k support is a >> non-issue for now. OTOH the many Python libraries depending on numpy >> might make Python 3K support happen sooner. > > Last I heard, the numpy folks think py-3 support is at least a year out. > Yes, I have seen that figure thrown around on the list last week, too. The reasoning seems to be that it would take until 2010 until "major" distributions shipped Py3K, but given the dependency of many libs I would be surprised if there wasn't enough pressure earlier to get this fixed. Given that numpy uses the Python C API directly this might be more work than some people think. In the end it would probably greatly help if the same codebase could support Python 2.x and Py3K at the same time, but we will see. Slightly OT: What is the preferred way to submit bug fixes? The sf tracker? I have two tiny build fixes for 0.98.3 (that also apply to 0.98.5) that fix the build on FreeBSD 7 and also works around some tcl/tl detection strangeness. Both patches are one liners to setupext.py. Cheers, Michael