1. 21 Aug, 2013 1 commit
  2. 17 Aug, 2013 1 commit
  3. 28 May, 2013 1 commit
  4. 12 May, 2013 3 commits
  5. 06 Apr, 2013 4 commits
  6. 03 Apr, 2013 1 commit
  7. 28 Mar, 2013 1 commit
  8. 23 Mar, 2013 3 commits
  9. 22 Mar, 2013 1 commit
  10. 21 Mar, 2013 3 commits
  11. 16 Mar, 2013 3 commits
  12. 11 Mar, 2013 3 commits
  13. 03 Feb, 2013 1 commit
    • Éric Araujo's avatar
      Add alias to restore 2.7.2 compatibility for setup scripts (#13994). · 4627dd08
      Éric Araujo authored
      The customize_compiler function moved many times during the 2.7 series;
      in 2.7.3, setup scripts importing this function from ccompiler were
      broken.  This commit restores compatibility without reintroducing the
      issue that #13994 originally fixed (duplication of the function).
      
      A unit test makes little sense here, as distutils tests never do imports
      in functions, and the fix is very simple.
      4627dd08
  14. 31 Jan, 2013 4 commits
    • doko@python.org's avatar
      9c2f75cb
    • Ned Deily's avatar
      null merge · 4379e7a0
      Ned Deily authored
      4379e7a0
    • Ned Deily's avatar
      Issue #13590: OS X Xcode 4 - improve support for universal extension modules · 2374a4cc
      Ned Deily authored
          In particular, fix extension module build failures when trying to use
          32-bit-only installer Pythons on systems with Xcode 4 (currently
          OS X 10.8, 10.7, and optionally 10.6).
          * Backport 3.3.0 fixes to 3.2 branch (for release in 3.2.4)
          * Since Xcode 4 removes ppc support, extension module builds now
            check for ppc compiler support and by default remove ppc and
            ppc64 archs when they are not available.
          * Extension module builds now revert to using system installed
            headers and libs (/usr and /System/Library) if the SDK used
            to build the interpreter is not installed or has moved.
          * Try to avoid building extension modules with deprecated
            and problematic Apple llvm-gcc compiler.  If original compiler
            is not available, use clang instead by default.
      2374a4cc
    • Ned Deily's avatar
      Issue #13590: OS X Xcode 4 - improve support for universal extension modules · 30f6c6e3
      Ned Deily authored
          In particular, fix extension module build failures when trying to use
          32-bit-only installer Pythons on systems with Xcode 4 (currently
          OS X 10.8, 10.7, and optionally 10.6).
          * Backport 3.3.0 fixes to 2.7 branch (for release in 2.7.4)
          * Since Xcode 4 removes ppc support, extension module builds now
            check for ppc compiler support and by default remove ppc and
            ppc64 archs when they are not available.
          * Extension module builds now revert to using system installed
            headers and libs (/usr and /System/Library) if the SDK used
            to build the interpreter is not installed or has moved.
          * Try to avoid building extension modules with deprecated
            and problematic Apple llvm-gcc compiler.  If original compiler
            is not available, use clang instead by default.
      30f6c6e3
  15. 27 Jan, 2013 3 commits
  16. 25 Jan, 2013 1 commit
  17. 28 Dec, 2012 2 commits
  18. 18 Dec, 2012 3 commits
  19. 09 Dec, 2012 1 commit