[Python-Dev] cpython (2.7): - Issue #17086: Backport the patches from the 3.3 branch to cross-build
Antoine Pitrou
solipsis at pitrou.net
Thu Feb 7 10:10:29 CET 2013
More information about the Python-Dev mailing list
Thu Feb 7 10:10:29 CET 2013
- Previous message: [Python-Dev] cpython (2.7): - Issue #17086: Backport the patches from the 3.3 branch to cross-build
- Next message: [Python-Dev] cpython (2.7): - Issue #17086: Backport the patches from the 3.3 branch to cross-build
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le Wed, 6 Feb 2013 16:08:39 -0500, Barry Warsaw <barry at python.org> a écrit : > On Feb 06, 2013, at 02:38 PM, Antoine Pitrou wrote: > > >Le Mon, 04 Feb 2013 21:04:39 +0100, > >Matthias Klose <doko at ubuntu.com> a écrit : > >> So what I do understand, build-related issues like an arm64 or > >> mingw32 port are ok for 2.7, if they are stable on the trunk, and > >> communicated on python-dev? > > > >Making Python build on a new platform is, AFAICT, considered a new > >feature, not a bugfix. For example, we support new MSVC versions in > >the main development branch, not in bugfix branches. > > Except that 2.7 is an exception to that since it's the last of the > Python 2 series, and has a much longer lifespan than normal > releases. I'm pretty sure we agreed that there would be some > exceptions for issues like new platforms for 2.7. Well, apparently we didn't make such an exception for MSVC :-) Regards Antoine.
- Previous message: [Python-Dev] cpython (2.7): - Issue #17086: Backport the patches from the 3.3 branch to cross-build
- Next message: [Python-Dev] cpython (2.7): - Issue #17086: Backport the patches from the 3.3 branch to cross-build
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list