Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-October/122166.html below:

[Python-Dev] Bumping autoconf from 2.68 to 2.69

• Previous message: [Python-Dev] [Python-checkins] cpython (2.7): don't expect warnings from doctests if they can't run
• Next message: [Python-Dev] Bumping autoconf from 2.68 to 2.69
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    Any objections to regenerating configure with autoconf 2.69?  The
    current version is based off 2.68, which was release on the 22nd
    of September 2010.  2.69 was released on the 24th of April, 2012.

    (There are some fixes for the more esoteric UNIX platforms that
     Snakebite will benefit from.  Also, I struggled to find a box
     with 2.68 even installed when I needed to regenerate configure
     this weekend; it seems all package management/ports have bumped
     to 2.69.)

    If there are no objections, can it be applied across the board?
    2.7, 3.2, 3.3 and 3.x?

        Trent.

• Previous message: [Python-Dev] [Python-checkins] cpython (2.7): don't expect warnings from doctests if they can't run
• Next message: [Python-Dev] Bumping autoconf from 2.68 to 2.69
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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