Visitar URL original
It would be great if we can clarify which Python versions are still maintained ... · Issue #1302 · python/pythondotorg · GitHub
Skip to content

It would be great if we can clarify which Python versions are still maintained ... #1302

Description

@Mariatta

... and which ones are not.

Is your feature request related to a problem? Please describe.
Folks not involved with Core Python development might not know which Python versions are still maintained, and which ones are no longer maintained and not preferred anymore.

We have a release schedule listed at the bottom of python.org/downloads, I guess it was meant to indicate which ones will still receive new fixes, but it was not explicit in saying that the other ones aren't being maintained anymore.

Devguide has some more info about it, but casual users wouldn't land on that page.

Describe the solution you'd like
It would be great if we can clarify which Python versions are still maintained, and which are not.
The downloads page seems like a good place. Perhaps we can add some paragraph indicating which ones are still actively maintained, and which ones are not.
We also should state that unmaintained Python versions should not be used.

Additional context
See twitter thread: https://twitter.com/pydanny/status/1024302657161256960

Activity

  1. jefftriplett commented on Jul 31, 2018

    @jefftriplett
    Member

    Would it make send to update the release grid from the downloads page to show whether or not a release is supported?

    Here is a screenshot: This could be an extra column/icon.

  2. jaap3 commented on Aug 1, 2018

    @jaap3
    Contributor

    What about doing something similar to Django's download page?

    They make a clear distinction between

    • Latest releases
      final and RC
    • Previous releases
      Currently only the LTS version
    • Unsupported previous releases
      With a clear indication that these releases "no longer receive security updates or bug fixes"

    Furthermore they do an excellent job of communicating the timeline of supported versions.

  3. anlutro commented on Sep 15, 2018

    @anlutro

    Was directed here from bugs.python.org, want to re-iterate my points because I think this is important. Every time I see people asking questions about this in IRC I have a hard time finding the official list.

    There are many pretty version support pages out there but I don't think that's the most important thing. Try searching for the following in google:

    • $THING versions support
    • $THING versions lifecycle
    • $THING versions roadmap
    • $THING versions end of life

    If you try these with PHP, Symfony, Django and Python, you'll go from the results being great to mediocre to absolutely terrible. Some of the Python search results even direct to a page on the devguide which only has old versions listed. If the table from the devguide was copied to somewhere on python.org and a little bit of attention is given to SEO that would help tremendously.

  4. berkerpeksag commented on Sep 15, 2018

    @berkerpeksag
    Member

    Thanks for the all comments. They all sound good to me. I'm planning to redesign downloads application (the first step is to retire v1 of downloads API) and I will incorporate all of these suggestions.

  5. mtbc commented on May 8, 2019

    @mtbc

    It was indeed only through https://bugs.python.org/issue25296 that I finally found what I wanted at https://devguide.python.org/#status-of-python-branches

  6. changeling commented on Jun 6, 2019

    @changeling

    [UPDATE: I just realized it's right there on the top level of https://devguide.python.org/. Which is great, though it still took me awhile. I first checked PEP 478, assuming that would be the canonical source. Then I looked at https://devguide.python.org/devcycle/, assuming that chart would include projected. Then I decided to just ask google, which didn't help. Basically, I missed that top-level devguide would have it, then PEP 478, then I went into rabbit-hole. So I guess what I'd suggest is that branch PEP, at the very least, should cover lifecycle. And perhaps have life-cycle points added to the download grid.]

    This seems to still be an issue. SEO seems pretty solid for PEPs, but as far as I can discover, projected EOL is absent from those.. For an example, acting as a non-savvy end user and doing google searches, can you find EOL for 3.5? I can't. Generally, EOLed branches are fairly discoverable, but future EOL is hit or miss.

    https://devguide.python.org/devcycle/ lists past EOL, but not projected.

    (What is 3.5 EOL? That's not even mentioned on PEP 478 -- Python 3.5 Release Schedule itself. @larryhastings?)

  7. Mariatta commented on Jun 8, 2019

    @Mariatta
    MemberAuthor

    3.5 EOL is September 13, 2020, documented in the devguide https://devguide.python.org/#status-of-python-branches

  8. added
    contentRelates to (un)published content on the site
    app/pagesRelates to the pages app
    psf-reviewThis should be reviewed by a PSF employee/member
    on Aug 11, 2019
  9. hugovk commented on Oct 13, 2019

    @hugovk
    Member

    What about doing something similar to Django's download page?

    Yes, that's a good one. Other projects with short, simple, clear, dedicated pages:

    PHP

    image


    Node.js

    image


    And @di just made a really good chart for Python:

    image

    https://python-release-cycle.glitch.me/

    I occasionally refer to the PHP and Node.js pages, they're easy to find and communicate immediately what I want to know.

    How about a similar "supported versions" page for Python with this or a similar chart?

  10. crwilcox commented on Dec 21, 2019

    @crwilcox
    Contributor

    I tried adding a table to the existing downloads page and I have this in a branch on my fork: https://github.com/crwilcox/pythondotorg/tree/add-release-schedule-to-downloads

    While not in the branch, I think ideally the python version column would link to the latest patch release.

    image

  11. brainwane commented on May 28, 2020

    @brainwane

    Thank you @berkerpeksag !

  12. hugovk commented on Dec 6, 2022

    @hugovk
    Member

    Update: a release cycle chart is now live at https://devguide.python.org/versions/

    image

    Re: issue python/docs-community#67 / PR python/devguide#988

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    app/pagesRelates to the pages appcontentRelates to (un)published content on the sitepsf-reviewThis should be reviewed by a PSF employee/member

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions