RELEASED Python 3.0rc3

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Barry Warsaw
    #1

    RELEASED Python 3.0rc3

    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1

    On behalf of the Python development team and the Python community, I
    am happy to announce the third and last planned release candidate for
    Python 3.0.

    This is a release candidate, so while it is not quite suitable for
    production environments, we strongly encourage you to download and
    test this release on your software. We expect only critical bugs to
    be fixed between now and the final release, currently planned for 03-
    Dec-2008.

    If you find things broken or incorrect, please submit bug reports at

    List of issues - Python tracker
    http://bugs.python.org


    Please read the RELNOTES file in the distribution for important
    details about this release. For more information and downloadable
    distributions, see the Python 3.0 website:

    http://www.python.org/download/releases/3.0/


    See PEP 361 for release schedule details:

    PEP 361 – Python 2.6 and 3.0 Release Schedule | peps.python.org
    http://www.python.org/dev/peps/pep-0361/
    This document describes the development and release schedule for Python 2.6 and 3.0. The schedule primarily concerns itself with PEP-sized items. Small features may be added up to and including the first beta release. Bugs may be fixed until the fina...


    Enjoy,
    - -Barry

    Barry Warsaw
    barry@python.or g
    Python 2.6/3.0 Release Manager
    (on behalf of the entire python-dev team)

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (Darwin)

    iQCVAwUBSSbOhHE jvBPtnXfVAQLzBw P/dS2j4XhZMNdb28T G3ZblkSmlPS4IU2 0U
    Vvq85inUkJ6idwK ZBqa6brrD1hbqrl 4UjKZh4/ppzhIwsJtFMlMiq nkHVrvIYFBG
    Yg+pQdO5HQzrw9K 04aTdtNiKTiiJNI kqWdQQUd573XBFO DRAIaq0qwk9C24k XeZM
    e3xNgNRxfmY=
    =TvxY
    -----END PGP SIGNATURE-----
    Tags: None
    • Mensanator
      #2
      Re: RELEASED Python 3.0rc3

      On Nov 21, 9:06 am, Barry Warsaw <ba...@python.o rgwrote:
      -----BEGIN PGP SIGNED MESSAGE-----
      Hash: SHA1
      >
      On behalf of the Python development team and the Python community, I  
      am happy to announce the third and last planned release candidate for  
      Python 3.0.
      >
      This is a release candidate, so while it is not quite suitable for  
      production environments, we strongly encourage you to download and  
      test this release on your software.  We expect only critical bugs to  
      be fixed between now and the final release, currently planned for 03-
      Dec-2008.
      I'm getting confused. Final release will just say Python 3.0, right?

      And 2.6 is in final release? So when ActiveState speaks of 2.6.0.0
      they mean a final release?

      So, if the IDLE from ActiveState comes up and says 2.6 (indicating
      final release), shouldn't the copywrite message also say 2.6
      instead of 2.6rc1 as shown here?


      Python 2.6rc1 (r26rc1:66438, Sep 13 2008, 09:20:38) [MSC v.1500 32
      bit
      (Intel)] on win32
      Type "copyright" , "credits" or "license()" for more information.

      *************** *************** *************** *************** ****
      Personal firewall software may warn about the connection IDLE
      makes to its subprocess using this computer's internal loopback
      interface. This connection is not visible on any external
      interface and no data is sent to or received from the Internet.
      *************** *************** *************** *************** ****

      IDLE 2.6




        Comment

        Previous template Next
        Working...