Once 7 Jun 2014 06:19, "Nick Coghlan" <ncoghlan at gmail.com> wrote: > > On 7 June 2014 15:05, Donald Stufft <donald at stufft.io> wrote: > > I don’t particularly care too much though, I just think that bumping > > the compiler in a 2.7.Z release is a really bad idea and that either > > of the other two options are massively better. > > It is *incredibly* unlikely that backwards compatibility with binary > extensions will be broken within the Python 2.7 series - there's a > reason we said "No" when the Stackless folks were asking about it a > while back. Instead, the toolchain availability problem is currently > being tackled by trying to make suitable build toolchains more readily > available (both the official VS 2008 toolchain and alternative open > source toolchains), and by reducing the reliance on building from > source for end users. A third piece of the puzzle could potentially be the availability of automated wheel-building services. (Personally I still haven't successfully managed to build windows wheels for my own packages, and envy my R-using colleagues whose PyPi equivalent does the building for them.) -n -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20140607/05b87038/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4