diff options
author | Martin Panter <vadmium+py@gmail.com> | 2017-01-29 10:09:43 +0000 |
---|---|---|
committer | Martin Panter <vadmium+py@gmail.com> | 2017-01-29 10:09:43 +0000 |
commit | 6d1d733828b49eb03d45da81c6b8c6b849fbc5df (patch) | |
tree | b0b120d6c527fb8cf6e4a0f175556611673ad780 /README | |
parent | 357e8cdc9b1c5a99be9ade2b1070c38d50ddadc6 (diff) | |
parent | 23282e54fdd766945930006ab606641a2db37a4c (diff) | |
download | cpython-6d1d733828b49eb03d45da81c6b8c6b849fbc5df.tar.gz |
Issues #29349: Merge Py 2 fix 3.5
Diffstat (limited to 'README')
-rw-r--r-- | README | 55 |
1 files changed, 28 insertions, 27 deletions
@@ -1,5 +1,5 @@ -This is Python version 3.5.3 -============================ +This is Python version 3.6.1 release candidate 1 +================================================ Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 Python Software Foundation. All rights @@ -29,9 +29,9 @@ find out more. On OSX and Cygwin, the executable is called python.exe; elsewhere it's just python. On Mac OS X, if you have configured Python with --enable-framework, you should -use "make frameworkinstall" to do the installation. Note that this installs -the Python executable in a place that is not normally on your PATH, you may -want to set up a symlink in /usr/local/bin. +use "make frameworkinstall" to do the installation. Note that this installs the +Python executable in a place that is not normally on your PATH, you may want to +set up a symlink in /usr/local/bin. On Windows, see PCbuild/readme.txt. @@ -90,9 +90,9 @@ What's New ---------- We have a comprehensive overview of the changes in the "What's New in -Python 3.5" document, found at +Python 3.6" document, found at - http://docs.python.org/3.5/whatsnew/3.5.html + https://docs.python.org/3.6/whatsnew/3.6.html For a more detailed change log, read Misc/NEWS (though this file, too, is incomplete, and also doesn't list anything merged in from the 2.7 @@ -105,9 +105,9 @@ entitled "Installing multiple versions". Documentation ------------- -Documentation for Python 3.5 is online, updated daily: +Documentation for Python 3.6 is online, updated daily: - http://docs.python.org/3.5/ + https://docs.python.org/3.6/ It can also be downloaded in many formats for faster access. The documentation is downloadable in HTML, PDF, and reStructuredText formats; the latter version @@ -117,7 +117,7 @@ formatting requirements. If you would like to contribute to the development of Python, relevant documentation is available at: - http://docs.python.org/devguide/ + https://docs.python.org/devguide/ For information about building Python's documentation, refer to Doc/README.txt. @@ -132,7 +132,7 @@ backported versions of certain key Python 3.x features. A source-to-source translation tool, "2to3", can take care of the mundane task of converting large amounts of source code. It is not a complete solution but is complemented by the deprecation warnings in 2.6. See -http://docs.python.org/3.5/library/2to3.html for more information. +https://docs.python.org/3.6/library/2to3.html for more information. Testing @@ -162,17 +162,17 @@ Installing multiple versions On Unix and Mac systems if you intend to install multiple versions of Python using the same installation prefix (--prefix argument to the configure script) -you must take care that your primary python executable is not overwritten by -the installation of a different version. All files and directories installed -using "make altinstall" contain the major and minor version and can thus live -side-by-side. "make install" also creates ${prefix}/bin/python3 which refers -to ${prefix}/bin/pythonX.Y. If you intend to install multiple versions using -the same prefix you must decide which version (if any) is your "primary" -version. Install that version using "make install". Install all other -versions using "make altinstall". - -For example, if you want to install Python 2.6, 2.7 and 3.5 with 2.7 being the -primary version, you would execute "make install" in your 2.7 build directory +you must take care that your primary python executable is not overwritten by the +installation of a different version. All files and directories installed using +"make altinstall" contain the major and minor version and can thus live +side-by-side. "make install" also creates ${prefix}/bin/python3 which refers to +${prefix}/bin/pythonX.Y. If you intend to install multiple versions using the +same prefix you must decide which version (if any) is your "primary" version. +Install that version using "make install". Install all other versions using +"make altinstall". + +For example, if you want to install Python 2.7, 3.5, and 3.6 with 3.6 being the +primary version, you would execute "make install" in your 3.6 build directory and "make altinstall" in the others. @@ -182,7 +182,7 @@ Issue Tracker and Mailing List We're soliciting bug reports about all aspects of the language. Fixes are also welcome, preferably in unified diff format. Please use the issue tracker: - http://bugs.python.org/ + https://bugs.python.org/ If you're not sure whether you're dealing with a bug or a feature, use the mailing list: @@ -191,23 +191,23 @@ mailing list: To subscribe to the list, use the mailman form: - http://mail.python.org/mailman/listinfo/python-dev/ + https://mail.python.org/mailman/listinfo/python-dev/ Proposals for enhancement ------------------------- If you have a proposal to change Python, you may want to send an email to the -comp.lang.python or python-ideas mailing lists for inital feedback. A Python +comp.lang.python or python-ideas mailing lists for initial feedback. A Python Enhancement Proposal (PEP) may be submitted if your idea gains ground. All current PEPs, as well as guidelines for submitting a new PEP, are listed at -http://www.python.org/dev/peps/. +https://www.python.org/dev/peps/. Release Schedule ---------------- -See PEP 478 for release details: http://www.python.org/dev/peps/pep-0478/ +See PEP 494 for release details: https://www.python.org/dev/peps/pep-0494/ Copyright and License Information @@ -231,3 +231,4 @@ so it may be used in proprietary projects. There are interfaces to some GNU code but these are entirely optional. All trademarks referenced herein are property of their respective holders. + |