It's Python 2. Not sure why anyone's writing Python 2 in 2023, but it's valid code.
Python
Welcome to the Python community on the programming.dev Lemmy instance!
π Events
October 2023
- PyConES Canarias 2023, 6-8th
- DjangoCon US 2023, 16-20th (!django π¬)
November 2023
- PyCon Ireland 2023, 11-12th
- PyData Tel Aviv 2023 14th
Past
July 2023
- PyDelhi Meetup, 2nd
- PyCon Israel, 4-5th
- DFW Pythoneers, 6th
- Django Girls Abraka, 6-7th
- SciPy 2023 10-16th, Austin
- IndyPy, 11th
- Leipzig Python User Group, 11th
- Austin Python, 12th
- EuroPython 2023, 17-23rd
- Austin Python: Evening of Coding, 18th
- PyHEP.dev 2023 - "Python in HEP" Developer's Workshop, 25th
August 2023
- PyLadies Dublin, 15th
- EuroSciPy 2023, 14-18th
September 2023
- PyData Amsterdam, 14-16th
- PyCon UK, 22nd - 25th
π Python project:
- Python
- Documentation
- News & Blog
- Python Planet blog aggregator
π Python Community:
- #python IRC for general questions
- #python-dev IRC for CPython developers
- PySlackers Slack channel
- Python Discord server
- Python Weekly newsletters
- Mailing lists
- Forum
β¨ Python Ecosystem:
π Fediverse
Communities
- #python on Mastodon
- c/django on programming.dev
- c/pythorhead on lemmy.dbzer0.com
Projects
- PythΓΆrhead: a Python library for interacting with Lemmy
- Plemmy: a Python package for accessing the Lemmy API
- pylemmy pylemmy enables simple access to Lemmy's API with Python
- mastodon.py, a Python wrapper for the Mastodon API
Feeds
Some people have legacy codebases and haven't been able to justify the workload to migrate it πππ
So common in consulting. Many customers only want new things and feel like they shouldn't have to keep paying once an initial product has been delivered. But needs change, tech moves on and things need refreshing or replacing. The hardest situation is when the client has no in-house expertise so can only assume you're trying to fleece them for more money.
The print call there is from python 2. I can do some editing to add in the brackets in a bit
I was a little cheeky there. But in all seriousness python 2 is End-of-Life and no one should use it anymore.
Come on, Python 2 only has 16 critical vulnerabilities. Live dangerously π.
Shoutouts to all people out there maintaining legacy code π«£
Although "critical" by CVE standards could just mean ReDoS for some non user facing code and which clearly is not a security issue but still of course requires urgent dependabot warnings on some parent package which doesn't even use the not at all vulnerable code anyway...