Re: [Python-Dev] [Python-checkins] peps: PEP for updating the URL layout on docs.python.org
On Sun, Oct 28, 2012 at 4:34 AM, Georg Brandl
Am 28.10.2012 12:29, schrieb Chris Jerdonek: ... I understand "latest" to mean "latest stable plus bugfixes". I.e., /3/ is 3.3.0+. /dev and /3.4 is 3.4a0. It might need clarifying in the PEP. ...
There's a slight mismatch with how we're doing it today because "http://docs.python.org/3/" shows 3.3.0 in the title even though it's the in-progress 3.3.1. The title should perhaps reflect that it's post 3.3.0 (and similarly for the 2.7 and 3.2 pages).
Well, that has always been the case, and it doesn't matter anyway, because generally there's nothing in 3.3.1, feature-wise, that won't have been in 3.3.0.
One reason to change would be to avoid possible confusion created on pages like this-- http://docs.python.org/3.3/whatsnew/3.2.html where it says-- Author: Raymond Hettinger Release: 3.3.0 Date: October 27, 2012 Would there be any disadvantage to changing the in-development titles to read something like 3.3.0+, etc? --Chris
Am 28.10.2012 13:19, schrieb Chris Jerdonek:
On Sun, Oct 28, 2012 at 4:34 AM, Georg Brandl
wrote: Am 28.10.2012 12:29, schrieb Chris Jerdonek: ... I understand "latest" to mean "latest stable plus bugfixes". I.e., /3/ is 3.3.0+. /dev and /3.4 is 3.4a0. It might need clarifying in the PEP. ...
There's a slight mismatch with how we're doing it today because "http://docs.python.org/3/" shows 3.3.0 in the title even though it's the in-progress 3.3.1. The title should perhaps reflect that it's post 3.3.0 (and similarly for the 2.7 and 3.2 pages).
Well, that has always been the case, and it doesn't matter anyway, because generally there's nothing in 3.3.1, feature-wise, that won't have been in 3.3.0.
One reason to change would be to avoid possible confusion created on pages like this--
http://docs.python.org/3.3/whatsnew/3.2.html
where it says--
Author: Raymond Hettinger Release: 3.3.0 Date: October 27, 2012
Well, that block is a little silly anyway. I would just delete the "Release" and "Date" lines.
Would there be any disadvantage to changing the in-development titles to read something like 3.3.0+, etc?
I'm not sure it would lower any confusion, instead of creating more. ("What is that + anyway? Do I need another version?" etc.) Georg
On Sun, 28 Oct 2012 05:19:26 -0700
Chris Jerdonek
One reason to change would be to avoid possible confusion created on pages like this--
http://docs.python.org/3.3/whatsnew/3.2.html
where it says--
Author: Raymond Hettinger Release: 3.3.0 Date: October 27, 2012
Would there be any disadvantage to changing the in-development titles to read something like 3.3.0+, etc?
Well, first why does it mention 3.3.0 while it's the what's new for 3.2? That's totally confusing, this mention should simply be removed. Also the date is not informative at all. Regards Antoine.
Am 28.10.2012 13:30, schrieb Antoine Pitrou:
On Sun, 28 Oct 2012 05:19:26 -0700 Chris Jerdonek
wrote: One reason to change would be to avoid possible confusion created on pages like this--
http://docs.python.org/3.3/whatsnew/3.2.html
where it says--
Author: Raymond Hettinger Release: 3.3.0 Date: October 27, 2012
Would there be any disadvantage to changing the in-development titles to read something like 3.3.0+, etc?
Well, first why does it mention 3.3.0 while it's the what's new for 3.2? That's totally confusing, this mention should simply be removed. Also the date is not informative at all.
Agreed, I've now removed them. Georg
On Sun, Oct 28, 2012 at 5:39 AM, Georg Brandl
Am 28.10.2012 13:30, schrieb Antoine Pitrou:
Well, first why does it mention 3.3.0 while it's the what's new for 3.2? That's totally confusing, this mention should simply be removed. Also the date is not informative at all.
Agreed, I've now removed them.
Thanks a lot. Many of the index pages linked from the table of contents also have uninformative release and date lines, e.g. http://docs.python.org/3/library/index.html but they use ":Release: |version|" (minor version without micro version) instead of ":Release: |release|", so they're less likely to be construed as an actual release date (but still uninformative). --Chris
Am 28.10.2012 13:54, schrieb Chris Jerdonek:
On Sun, Oct 28, 2012 at 5:39 AM, Georg Brandl
wrote: Am 28.10.2012 13:30, schrieb Antoine Pitrou:
Well, first why does it mention 3.3.0 while it's the what's new for 3.2? That's totally confusing, this mention should simply be removed. Also the date is not informative at all.
Agreed, I've now removed them.
Thanks a lot. Many of the index pages linked from the table of contents also have uninformative release and date lines, e.g.
http://docs.python.org/3/library/index.html
but they use ":Release: |version|" (minor version without micro version) instead of ":Release: |release|", so they're less likely to be construed as an actual release date (but still uninformative).
Right. I think they are remnants from the LaTeX age; you can remove them all if you want. Georg
On Sun, Oct 28, 2012 at 6:05 AM, Georg Brandl
Am 28.10.2012 13:54, schrieb Chris Jerdonek:
On Sun, Oct 28, 2012 at 5:39 AM, Georg Brandl
wrote: Am 28.10.2012 13:30, schrieb Antoine Pitrou:
Well, first why does it mention 3.3.0 while it's the what's new for 3.2? That's totally confusing, this mention should simply be removed. Also the date is not informative at all.
Agreed, I've now removed them.
Thanks a lot. Many of the index pages linked from the table of contents also have uninformative release and date lines, e.g.
http://docs.python.org/3/library/index.html
but they use ":Release: |version|" (minor version without micro version) instead of ":Release: |release|", so they're less likely to be construed as an actual release date (but still uninformative).
Right. I think they are remnants from the LaTeX age; you can remove them all if you want.
Great, I just removed them. --Chris
On 28/10/2012 12:39, Georg Brandl wrote:
Am 28.10.2012 13:30, schrieb Antoine Pitrou:
On Sun, 28 Oct 2012 05:19:26 -0700 Chris Jerdonek
wrote: One reason to change would be to avoid possible confusion created on pages like this--
http://docs.python.org/3.3/whatsnew/3.2.html
where it says--
Author: Raymond Hettinger Release: 3.3.0 Date: October 27, 2012
Would there be any disadvantage to changing the in-development titles to read something like 3.3.0+, etc?
Well, first why does it mention 3.3.0 while it's the what's new for 3.2? That's totally confusing, this mention should simply be removed. Also the date is not informative at all.
Agreed, I've now removed them.
Georg
Is it worth removing this as well, it's a couple of lines down "See also PEP 392 - Python 3.2 Release Schedule" ? -- Cheers. Mark Lawrence.
Am 28.10.2012 17:23, schrieb Mark Lawrence:
On 28/10/2012 12:39, Georg Brandl wrote:
Am 28.10.2012 13:30, schrieb Antoine Pitrou:
On Sun, 28 Oct 2012 05:19:26 -0700 Chris Jerdonek
wrote: One reason to change would be to avoid possible confusion created on pages like this--
http://docs.python.org/3.3/whatsnew/3.2.html
where it says--
Author: Raymond Hettinger Release: 3.3.0 Date: October 27, 2012
Would there be any disadvantage to changing the in-development titles to read something like 3.3.0+, etc?
Well, first why does it mention 3.3.0 while it's the what's new for 3.2? That's totally confusing, this mention should simply be removed. Also the date is not informative at all.
Agreed, I've now removed them.
Georg
Is it worth removing this as well, it's a couple of lines down
"See also PEP 392 - Python 3.2 Release Schedule" ?
Why? PEP 392 is not out of date, and for those who want to know when exactly 3.2 and its minor versions were released, it is useful. Georg
participants (4)
-
Antoine Pitrou
-
Chris Jerdonek
-
Georg Brandl
-
Mark Lawrence