| msg288976 - (view) |
Author: Inada Naoki (methane) *  |
Date: 2017-03-04 11:42 |
|
|
| See https://docs.python.org/3/whatsnew/3.6.html At top: :Release: |release |
:Date: |
today |
:Editors: Elvis Pranskevichus <elvis@magic.io>, Yury Selivanov <yury@magic.io> This |
today |
| msg288977 - (view) |
Author: Ned Deily (ned.deily) * |
Date: 2017-03-04 12:17 |
|
|
| It's a bit confusing but: 1. https://docs.python.org/3/whatsnew/3.6.html is the URL for the current 3.6 branch, in other words, what will be in the next 3.6 release. These are rebuilt as changes are checked in. 2. https://docs.python.org/release/3.6.0/whatsnew/3.6.html (which is linked from https://www.python.org/doc/versions/) is the URL for the docs corresponding to the 3.6.0 release. These are built at release time and then never change. Does that help? |
|
|
|
|
| msg288986 - (view) |
Author: Inada Naoki (methane) * |
Date: 2017-03-04 16:56 |
|
|
| > is the URL for the current 3.6 branch, in other words, what will be in the next 3.6 release. "next 3.6 release" means 3.6.1? > These are rebuilt as changes are checked in. There are some commit for fixing something after 3.6.0 released. But I think rebuild can be happen without changing the page. For example, major sphinx version up, fixing template, update version of imported js libraries. And as I said, the document may be built on other machine. In this case, this |today |
is not related to last commit date of this page. It seems unmeaningful. So I still this ":Date:" should be release date, or removed. |
|
|
|
| msg289055 - (view) |
Author: Ned Deily (ned.deily) * |
Date: 2017-03-06 02:15 |
|
|
| Sorry, I disagree. I think the point of adding these directives is that shows for what release of 3.6.x they apply. It is expected that the What's New documents may be updated during the lifecycle of a major release and having the release and date there lets the reader know that they are update. For example, at the moment https://docs.python.org/3.6/whatsnew/3.6.html shows: What’s New In Python 3.6 Release: 3.6.1rc1 Date: March 05, 2017 which is correct. |
|
|
|
|
| msg289056 - (view) |
Author: Inada Naoki (methane) * |
Date: 2017-03-06 02:18 |
|
|
| https://docs.python.org/3.7/whatsnew/3.6.html shows: Release: 3.7.0a0 Date: February 15, 2017 Is it make sense for you? |
|
|
|
|
| msg289057 - (view) |
Author: Inada Naoki (methane) * |
Date: 2017-03-06 02:20 |
|
|
| Additonally, unlike "changelog", "What's New" only shows difference between 3.5 and 3.6. It won't be updated to describe changes between 3.6.0 and 3.6.1. |
|
|
|
|
| msg289059 - (view) |
Author: Ned Deily (ned.deily) * |
Date: 2017-03-06 02:27 |
|
|
| > Additonally, unlike "changelog", "What's New" only shows difference between 3.5 and 3.6. It won't be updated to describe changes between 3.6.0 and 3.6.1. That's not always true. There are occasionally changes made in the What's New document for maintenance releases. See, for example, https://docs.python.org/3.5/whatsnew/3.5.html. You'll find references to 3.5.1 and 3.5.2 there. If it's truly bothering people, a better solution is to just remove the release and date directives. They aren't there for earlier releases. We can live without them. |
|
|
|
|
| msg289060 - (view) |
Author: Inada Naoki (methane) * |
Date: 2017-03-06 02:28 |
|
|
| I'm sorry, I was wrong. https://docs.python.org/3.5/whatsnew/3.5.html asyncio has "Updates in 3.5.1:" section. provisional package will introduce updates in what's new in bugfix release. So is it OK to just removing Date and Release field? "Date (when this HTML is built)" and "Release (of branch this page is built)" are not good for "What's New In 3.6" page. |
|
|
|
|
| msg289061 - (view) |
Author: Ned Deily (ned.deily) * |
Date: 2017-03-06 02:29 |
|
|
| Heh, it looks like we agree! |
|
|
|
|
| msg290118 - (view) |
Author: Ned Deily (ned.deily) * |
Date: 2017-03-24 20:09 |
|
|
| New changeset 0acdea79cba3883c5e7035c7336fb0ce54435c03 by Ned Deily (INADA Naoki) in branch '3.6': bpo-29719: Remove Date and Release field in whatsnew/3.6 (GH-500) https://github.com/python/cpython/commit/0acdea79cba3883c5e7035c7336fb0ce54435c03 |
|
|
|
|
| msg290292 - (view) |
Author: Inada Naoki (methane) * |
Date: 2017-03-24 22:50 |
|
|
| New changeset 4e1a065c20856a00d0fe88ce022b249170608058 by INADA Naoki in branch '3.6': bpo-29719: Remove Date and Release field in whatsnew/3.6 (GH-500) https://github.com/python/cpython/commit/4e1a065c20856a00d0fe88ce022b249170608058 |
|
|
|
|
| msg290293 - (view) |
Author: Inada Naoki (methane) * |
Date: 2017-03-24 22:51 |
|
|
| New changeset 2225ddaa9e64c086b2b6997b0c9ac50921f7aa85 by INADA Naoki in branch 'master': bpo-29719: Remove Date and Release field in whatsnew/3.6 (GH-494) https://github.com/python/cpython/commit/2225ddaa9e64c086b2b6997b0c9ac50921f7aa85 |
|
|
|
|
| msg313711 - (view) |
Author: Cheryl Sabella (cheryl.sabella) * |
Date: 2018-03-12 23:00 |
|
|
| I believe this can be closed as 'fixed'? |
|
|
|
|
| msg313713 - (view) |
Author: Ned Deily (ned.deily) * |
Date: 2018-03-13 01:16 |
|
|
| New changeset a34510a4c562b4b23c7f9da6ff6e2318484f5f1a by Ned Deily in branch 'master': bpo-29719: Remove Date and Release field in whatsnew/3.7 and 8 (GH-6093) https://github.com/python/cpython/commit/a34510a4c562b4b23c7f9da6ff6e2318484f5f1a |
|
|
|
|
| msg313714 - (view) |
Author: Ned Deily (ned.deily) * |
Date: 2018-03-13 01:16 |
|
|
| New changeset d461ed84b57aae0bdccd117dc38109c087444d50 by Ned Deily in branch '3.7': bpo-29719: Remove Date and Release field in whatsnew/3.7 (GH-6094) https://github.com/python/cpython/commit/d461ed84b57aae0bdccd117dc38109c087444d50 |
|
|
|
|
| msg313715 - (view) |
Author: Ned Deily (ned.deily) * |
Date: 2018-03-13 01:23 |
|
|
| > I believe this can be closed as 'fixed'? Well, it *was* fixed! But then I reintroduced the boilerplate when I created the 3.7 and 3.8 whatsnew files - now fixed. Thanks for the reminder! |
|
|
|
|