By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
439,941 Members | 1,766 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 439,941 IT Pros & Developers. It's quick & easy.

RELEASED Python 3.0rc3

P: n/a
-----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

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:

http://www.python.org/dev/peps/pep-0361/

Enjoy,
- -Barry

Barry Warsaw
ba***@python.org
Python 2.6/3.0 Release Manager
(on behalf of the entire python-dev team)

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

iQCVAwUBSSbOhHEjvBPtnXfVAQLzBwP/dS2j4XhZMNdb28TG3ZblkSmlPS4IU20U
Vvq85inUkJ6idwKZBqa6brrD1hbqrl4UjKZh4/ppzhIwsJtFMlMiqnkHVrvIYFBG
Yg+pQdO5HQzrw9K04aTdtNiKTiiJNIkqWdQQUd573XBFODRAIa q0qwk9C24kXeZM
e3xNgNRxfmY=
=TvxY
-----END PGP SIGNATURE-----
Nov 21 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Nov 21, 9:06*am, Barry Warsaw <ba...@python.orgwrote:
-----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


Nov 22 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.