Time for python 4. Python 3 to sunset in 2025!
Sunsetting Python 2
271–280 of 733 posts
Re: Sunsetting Python 2
#272One thing that confuses me about Python is just how many projects don't specify if the app is supposed to use 2 or 3, and the correct answer isn't 'either'. Check out something from Github, only to find I actually do need Python 2.7 or something. Is it that Python developers assume everyone will just intuit the version, or is there a default?
It's usually specified in setup.py.
Re: Sunsetting Python 2
#273Does someone know if there is a way to compile python programs to some sort of static binary?
I have a GPS watch and some old Python 2 script to export the data (found it online (unmaintained) a few years ago).
However, when Python 2 will be sunsetted I am a bit worried that Linux distributions will stop packaging the dependencies of said script, but I would like to keep using it until the watch breaks.
Re: Sunsetting Python 2
#274Earlier quoted context omitted.
> For my personal use case at least, this timeline worked out well for me. Hint for Hacker News commenters: 99% of the time, if your phrase includes the term "use case", you can safely just delete it and lose no meaning. It's just a way to say "for me" or "for them" that sounds more technical but really isn't. In this case, you could say "This timeline worked out well for me".
Are you sure you are indeed a normal human?
[deleted]
Re: Sunsetting Python 2
#275I long for the day when typing "python" into a shell will bring up a python 3 prompt
Switch to Arch Linux and live the dream. It has had python3 as /usr/bin/python since 2010. https://www.archlinux.org/news/python-is-now-python-3/
Also Gentoo since mid-2018.
Although their package management requires manually specifying the minimum accepted Python version for every single package, so they have thousands of packages that would run just fine on Python 3.7 but no one has the time to manually check and label them as such. So their default is still 3.6 and using 3.7 as your default version is not well supported.
I wish someone told me Gentoo is a non-starter before I wasted an afternoon installing it.
While we're on the topic, it's pretty stupid how PEP 394, the one that says "python should point to python2.7", gives its reasoning as "because all Linux distros except Arch do it this way" and then all the distros say "python should be python2 because the PEP says so" for the next 9 (maybe more) years. How is anything ever supposed to change?
Re: Sunsetting Python 2
#276And now remind yourself that there are self driving cars out there and autonomous digging equipment that is based on ROS, which doesn't have any plan or intent to move to python 3. Fun stuff...
ROS 1.1 (next release) will target Python3 only. https://discourse.ros.org/t/versioning-roadmap-moveit-1-0-re...
Thats not true, you're referencing the ROS wiki page of the MoveIt! Planning package, which has nothing to do with ROS other than using it.
Widespread Python3 adoption is planned for ROS 2 which has been vaporware for the last 3 years.
Re: Sunsetting Python 2
#277Guessing some Python 2 users rebel and fork to provide security patches.
Re: Sunsetting Python 2
#278Earlier quoted context omitted.
>In 2015, there was no way I could have moved to Python 3. There were too many libraries I depended on that hadn't ported yet. You could work on porting them or be part of that effort?
Some people have full-time jobs and other obligations already that don't include time for this kind of effort.
Your employer should be pitching in your effort. If they're not, and they're choosing to be a bad citizen, then on their own heads be it.
Re: Sunsetting Python 2
#279Earlier quoted context omitted.
Yeah, Built Robotics[1] apparently does, at least according to their hiring page. And I think Audi is using it for their self driving cars... https://www.builtrobotics.com/
I mean hiring page doesn't mean they actually use it in the product. You can use ROS for designing the system, but in terms of performance it has issues if you try to use it in an embedded context. I still kind of doubt they have it running in their product.
Makeshift solutions last the longest, I'd highly doubt that they run 2 messaging systems side by side, thats just unrealistic for a startup. Especially considering that ROS is very invasive with it's MSG format and build tooling.
Re: Sunsetting Python 2
#280Earlier quoted context omitted.
Tongue in cheek comment; C was released 47 years ago and is still supported... but then again, that shows a very different philosophy between system languages and scripting languages.
Very few people write pre-ANSI C code today though, and the language itself was last updated in 2011. I'm sure people wouldn't gladly accept C code written for a 47-year-old compiler today.
> the language itself was last updated in 2011
The current standard languauge is C18.