Brian Curtin <br...@python.org> added the comment: Thanks for your report. Unfortunately Python 3.2 won't ever work in this way because changing compilers would be a new feature, and bug fix releases like 3.2 don't receive new features. Yesterday we completed the transition to VS2010 as a step towards our 3.3 release.
We are open to supporting VS11, but it won't become the standard compiler suite we use until VS11 goes RTM. I'm not aware of any release schedule announced yet, but I believe we would need VS11 to be released before our first beta release, which is at the end of June. Most estimates I've seen don't look favorable for us supporting it in 3.3. Another issue that may hinder this is that myself, and as far as I know, the other developers, do not have ARM machines available to them. I'm interested in continuing our transition from VS2010 on to VS11 for when it's ready, but anything ARM related will likely require someone else to help out, maybe even you :) ---------- components: +Build, Windows -Interpreter Core versions: +Python 3.3, Python 3.4 -Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14802> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
