Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.002 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'subject:Python': 0.05; 'received:verizon.net': 0.07; 'terry': 0.07; 'version?': 0.07; 'python': 0.08; 'curtin': 0.09; 'machines.': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:modules': 0.09; 'am,': 0.12; 'bit.': 0.16; 'devs': 0.16; 'reedy': 0.16; 'subject: \n ': 0.16; 'subject:which': 0.16; 'win64': 0.16; 'subject:Windows': 0.17; 'linux': 0.17; 'wrote:': 0.18; 'jan': 0.19; 'memory': 0.21; 'compiled': 0.21; 'header:In- Reply-To:1': 0.22; '(or': 0.22; 'gcc': 0.23; 'welcome.': 0.23; 'windows': 0.26; 'bit': 0.28; 'compile': 0.29; 'installing': 0.29; 'problem': 0.29; 'compiling': 0.30; 'loewis': 0.30; 'modules,': 0.30; 'yes.': 0.30; 'least': 0.30; 'martin': 0.31; 'subject:?': 0.31; 'actually': 0.31; 'version': 0.32; 'sort': 0.33; 'header :User-Agent:1': 0.33; 'header:X-Complaints-To:1': 0.34; 'rather': 0.34; 'running': 0.34; 'to:addr:python-list': 0.35; 'brian': 0.35; 'received:org': 0.36; 'basics': 0.37; 'but': 0.37; 'uses': 0.38; 'mass': 0.38; 'could': 0.38; 'data': 0.38; 'that.': 0.39; 'processing': 0.39; 'suggestions': 0.39; 'everyone': 0.39; 'subject: (': 0.40; 'to:addr:python.org': 0.40; 'release': 0.40; 'spend': 0.61; '2011': 0.61; 'studio': 0.63; 'our': 0.63; 'free': 0.64; 'believe': 0.65; 'limit': 0.67; 'edition': 0.68; 'compiles': 0.84; 'downloadable': 0.84; 'ms.': 0.84; '3.3': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Reedy Subject: Re: Compiling Python (modules) on 64bit Windows - which compiler suite? Date: Wed, 21 Mar 2012 13:56:20 -0400 References: <808abad4-3ab3-4336-8a31-2f88eb28be01@v22g2000vby.googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: pool-74-109-121-73.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 In-Reply-To: <808abad4-3ab3-4336-8a31-2f88eb28be01@v22g2000vby.googlegroups.com> X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 29 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1332352612 news.xs4all.nl 6918 [2001:888:2000:d::a6]:35979 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:21995 On 3/21/2012 11:06 AM, Ralph Heinkel wrote: > when processing our mass spectrometry data we are running against the > 2GB memory limit on our 32 bit machines. So we are planning to move to > 64bit. Downloading and installing the 64bit version of Python for > Windows is trivial, but how do we compile our own C extension? Visual C > ++ 2008 express comes for free, but only compiles for 32 bit. > > What has been used to compile the downloadable Python Win64 bit > version? Visual Studio professional? Yes. Python Windows devs get it for free from MS. > The problem with the professional edition is that it is hard to obtain > and it is sort of out-of-date - nowadays everyone uses Visual Studio > 2010 (or even 2011 coming soon). So if Visual Studio 2008 professional > is required for compiling 64bit modules, we would have to spend $1200 > for a license which is actually rather out of date. > > Any hints or suggestions are very welcome. I believe the intention is to release 3.3 compiled with VS 2010. Brian Curtin and Martin Loewis are working on that. I believe people have successfully built at least the basics with VS2010. You could also dual boot to Linux and get 64 bit gcc for free. -- Terry Jan Reedy