I still have to deal with #Python2 every day.
Everyone else?
And Python 2.7 is now gone from GitHub Actions! 🪦
https://github.com/actions/setup-python/issues/672#issuecomment-1602673800
Our commitment to #python2 projects and GitHub removing #python27 from their runners' tool cache have given us a reason to create the `coatldev/six` Docker image.
As of today, it comes with Python 3.10.11 and 2.7.18 pre-installed, and ready for running your tests and even build and upload your packages.
Why 3.10.11?
Because `mypy[python2]` cannot be installed on 3.11.
Who is using it?
Our friends at ignition-api.
Does it work?
Yes, it does.
Check it out here!
Next, GitHub will be removing support for Python 2.7 from actions/setup-python in under a month, on 19th June. 🪦
"Breaking changes
"Hello everyone. The Python 2.7.x will be removed from python-versions and it won't be possible to set up Python 2.7.x by setup-python.
"The motivation for the changes
"Python2.7 is not supported since January 1, 2020."
On May 15 #github will remove #python2 from all remaining actions/runner-images; this includes ubuntu-20.04 and windows-2019. But this is not the end.
If you're still maintaining `Python :: 2 :: Only` packages, feel free to use our brand new `python2-pypi-upload` action.
You may find it on the GitHub Marketplace using the following link:
Python 2.7 went EOL on 2020-01-01. 🪦
https://devguide.python.org/versions/
Github Actions and Azure DevOps will be dropping Python 2.7 starting 2023-05-15, taking 3-4 days for rollout. ⏳
"Possible impact
"If your builds depend on python2.7 they will be broken."
https://github.com/actions/runner-images/issues/7401
#GitHub #GitHubActions #Azure #AzureDevOps #Python #Python27 #CI #EOL
@thecesrom Jythooooooooon! In my best Kirk voice.
:java: and :python: together is a great idea, but not having the Python 3 `main` branch working, and having no clear progress makes it feel like Perl 6 all over again.
They should rename their moribund Jython3 repo, that's just confusing!
It's such a shame, useful Java scripting interfaces languishing in a dying ecosystem.
There was a similar lag with things that embed CPython, but they have an escape route.
Try tauthon, still supported:
RT https://twitter.com/osmose_qa
That's it! Osmose is now compatible with #Python3, and long before the Python 2.7 end of live countdown. First attempt fails years ago, second successes and it take just 5 months to do the migration. Ho, wait a minute, Osmose Frontend website is still in #Python27, open to help.