Path: csiph.com!goblin3!goblin1!goblin.stu.neva.ru!uio.no!news.tele.dk!news.tele.dk!small.news.tele.dk!newsgate.cistron.nl!newsgate.news.xs4all.nl!nzpost1.xs4all.net!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; 'installed.': 0.05; 'subject:build': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'extensions': 0.13; 'appropriate': 0.14; 'subject:python': 0.14; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'subject:windows': 0.16; 'looked': 0.16; 'changes': 0.20; '(or': 0.23; 'header:User- Agent:1': 0.26; 'header:X-Complaints-To:1': 0.26; 'guess': 0.31; 'supposed': 0.31; 'windows.': 0.33; 'there': 0.36; 'visual': 0.36; 'to:addr:python-list': 0.36; 'received:org': 0.37; 'release': 0.37; 'to:addr:python.org': 0.40; 'received:109': 0.75; 'becker': 0.84 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Robin Becker Subject: how to build windows extensions for python 3.5 Date: Mon, 14 Sep 2015 16:52:51 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: 109.174.168.73 X-Mozilla-News-Host: news://news.gmane.org:119 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.20+ 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: 7 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1442245980 news.xs4all.nl 23753 [2001:888:2000:d::a6]:47484 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:96571 I understand there have been changes to the way that extensions are supposed to be built for windows. Is there any user documentation regarding these changes? Last time I looked the appropriate Visual Studio hadn't been release so I guess I will need to use my MSDN skills (or incantations) to first get that installed. -- Robin Becker