RELEASED] Python 3.4.7rc1 and Python 3.5.4rc1 are now available
On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm relieved to announce the availability of Python 3.4.7rc1 and Python 3.5.4rc1.
Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. Python 3.4 now only receives security fixes, not bug fixes, and Python 3.4 releases are source code only--no more official binary installers will be produced.
Python 3.5.4 will be the final 3.5 release in "bug fix" mode. After 3.5.4 is released, Python 3.5 will also move into "security fixes mode".
Both these releases are "release candidates". They should not be considered the final releases, although the final releases should contain only minor differences. Python users are encouraged to test with these releases and report any problems they encounter.
You can find Python 3.4.7rc1 here:
https://www.python.org/downloads/release/python-347rc1/
And you can find Python 3.5.4rc1 here:
https://www.python.org/downloads/release/python-354rc1/
Python 3.4.7 final and Python 3.5.4 final are both scheduled for release on August 6th, 2017.
Happy Pythoning,
//arry/
On 25.07.2017 10:37, Larry Hastings wrote:
And you can find Python 3.5.4rc1 here:
https://www.python.org/downloads/release/python-354rc1/
Python 3.4.7 final and Python 3.5.4 final are both scheduled for release on August 6th, 2017.
the build of the documentation fails with at least the 3.5.4rc1. It adds a new build dependency (blurb), which is inconvenient to build on stable environments, or when pip is not available. Please could you consider including the blurb module itself in python for the stable branches?
The build of the docs then fails with:
make -C Doc html make[1]: Entering directory '/home/packages/python/3.5/python3.5-3.5.4~rc1/Doc' mkdir -p build PYTHONPATH=/home/packages/python/3.5/python3.5-3.5.4~rc1/debian/blurb python3 -m blurb merge -f build/NEWS Traceback (most recent call last): File "/usr/lib/python3.5/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/usr/lib/python3.5/runpy.py", line 85, in _run_code exec(code, run_globals) File "/home/packages/python/3.5/python3.5-3.5.4~rc1/debian/blurb/blurb.py", line 1602, in <module> main() File "/home/packages/python/3.5/python3.5-3.5.4~rc1/debian/blurb/blurb.py", line 1562, in main sys.exit(fn(*filtered_args, **kwargs)) File "/home/packages/python/3.5/python3.5-3.5.4~rc1/debian/blurb/blurb.py", line 970, in merge versions = glob_versions() File "/home/packages/python/3.5/python3.5-3.5.4~rc1/debian/blurb/blurb.py", line 284, in glob_versions with pushd("Misc/NEWS.d"): File "/home/packages/python/3.5/python3.5-3.5.4~rc1/debian/blurb/blurb.py", line 205, in __enter__ os.chdir(self.path) FileNotFoundError: [Errno 2] No such file or directory: 'Misc/NEWS.d' Makefile:42: recipe for target 'build' failed
there is no Doc/Misc/NEWS.d directory (neither a Misc/NEWS.d directory)
2017-07-25 12:23 GMT+02:00 Matthias Klose doko@ubuntu.com:
the build of the documentation fails with at least the 3.5.4rc1. It adds a new build dependency (blurb), which is inconvenient to build on stable environments, or when pip is not available. Please could you consider including the blurb module itself in python for the stable branches?
Sorry, I didn't look yet how blurb generates the documentation, but if blurb is deterministic and only generates files: would it be possible to include generated files in tarballs to prevent completely the need of blurb to build Python from a release tarball?
Victor
On Jul 25, 2017, at 06:50, Victor Stinner victor.stinner@gmail.com wrote:
2017-07-25 12:23 GMT+02:00 Matthias Klose doko@ubuntu.com:
the build of the documentation fails with at least the 3.5.4rc1. It adds a new build dependency (blurb), which is inconvenient to build on stable environments, or when pip is not available. Please could you consider including the blurb module itself in python for the stable branches?
Sorry, I didn't look yet how blurb generates the documentation, but if blurb is deterministic and only generates files: would it be possible to include generated files in tarballs to prevent completely the need of blurb to build Python from a release tarball?
Matthias has discovered a bug in the new process. The tarball does indeed already have a generated Misc/NEWS. The quandry is that the blurb generation step is needed when building the docs directly from the Git repo, including the daily website builds, but it should not be performed when building the Docs from a release tarball. Please open an issue for this on the tracker and mark it as "release blocker" so it can get sorted out before the final releases.
-- Ned Deily nad@python.org -- []
participants (4)
-
Larry Hastings -
Matthias Klose -
Ned Deily -
Victor Stinner