Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

End support for Python 2.7 #480

Closed
satterly opened this issue Feb 20, 2018 · 9 comments
Closed

End support for Python 2.7 #480

satterly opened this issue Feb 20, 2018 · 9 comments
Labels
enhancement New feature or request

Comments

@satterly
Copy link
Member

satterly commented Feb 20, 2018 •
edited
Loading

Python 2.7 is EOL in 2020 and many python projects have decided to stop supporting Python 2.7 already.

The benefits of a Python 3 only codebase means that Alerta projects can take advantage of new features such as type hints.

It is proposed to make Alerta Release 5.2 and all dependent projects the last release to support Python 2.7. The proposal is that Python 2.7 support should be dropped 6 months from now. ie. 31 August 2018.

From this date, all future Alerta releases (ie. 6.x etc) will only support Python 3 with the last Python 2 release (5.2.x) only getting critical bug fixes.
@mmulqueen mmulqueen mentioned this issue Feb 23, 2018
Merged
@mmulqueen
Copy link
Contributor

Fully agree with this proposal. We've been running Alerta with Python 3 since we've started using it, no issues. I've proposed some related changes to the documentation.

@satterly satterly mentioned this issue Apr 16, 2018
Closed
@satterly
Copy link
Member Author

satterly commented Apr 17, 2018 •
edited
Loading

Worryingly, I've just learned that Click is recommending Python 2 for production environments due to unresolved Python 3 limitations. See http://click.pocoo.org/5/python3/ Click is used by the alerta CLI.

@d-ganchar
Copy link
Contributor

Not sure that Python 2.7 support makes sense.
Better to use typing

@satterly
Copy link
Member Author

satterly commented May 9, 2018 •
edited
Loading

@d-ganchar Exactly. That's why python 2.7 support will be withdrawn in less than 4 months from now.

@satterly satterly added the enhancement New feature or request label Jul 4, 2018
@satterly
Copy link
Member Author

IMPORTANT Support for Alerta on Python 2.7 will end in one month!!!

@satterly
Copy link
Member Author

❗️ Note: An example of what needs to change in the deployment for an Apache/WSGI virtualenv environment on Debian/Ubuntu can be found here alerta/vagrant-try-alerta#13

@satterly
Copy link
Member Author

satterly commented Aug 23, 2018 •
edited
Loading

Alerta server version 5.2.9 has just been published to Pypy and it is proposed that this is the last release to support Python 2.7. Only critical application bug fixes and security fixes will be applied to this branch in future.

Alerta server 6.0 will only support Python 3.5+ and will require Postgres 9.5+ or MongoDB 3.x.

@satterly
Copy link
Member Author

satterly commented Aug 24, 2018 •
edited
Loading

Alerta client version 5.2.1 has just been published to Pypy and it will be the last release to support Python 2.7. Only critical application bug fixes and security fixes will be applied to this branch in future.

@satterly satterly mentioned this issue Aug 24, 2018
Closed
@satterly
Copy link
Member Author

satterly commented Sep 4, 2018 •
edited
Loading

Limited support for Alerta on Python 2.7 will continue until support for Python 2.7 is officially dropped.

screen shot 2018-09-04 at 10 24 58

https://pythonclock.org/

@satterly satterly closed this as completed Sep 4, 2018
@satterly satterly mentioned this issue Sep 4, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@satterly @mmulqueen @d-ganchar