Honestly it's about time. I've been annoyed at having to maintain two versions of python.
Sunsetting Python 2
241–250 of 733 posts
Re: Sunsetting Python 2
#242Every now and then a language like no other pops up: it's use is unusual and unusually long. Various biblical languages come to mind: Latin, Church Slavonic, Hebrew at one point. These languages are feature complete, and the fact that they didn't change was their main appeal. I've always thought Python 2 might be headed for the languages. Which is fine, it's great to have a programming equivalent of Latin.
... I'm sorry, but wouldn't the Latin equivalent be C... given Python is written in it, and most languages syntax is born from it. Python is more like the English language... it's borrowed a bunch of stuff from many different languages and isn't even compatible with itself ;) (2 vs 3). I mean, this is assuming with thing spoken languages are even at all similar to programming languages... which I don't think they are…
C is a great example of a Latin too, agreed. There can be multiple ;)
Re: Sunsetting Python 2
#243Re: Sunsetting Python 2
#244Earlier quoted context omitted.
This x 1000. “The free libraries we chose to depend upon haven’t migrated.” Do you have programmers? “Of course.” Put them to work. “We have other priorities.” Well then. Your choice, your outcome.
This attitude is ridiculous. I'm supposed to go and tell all the various projects that I depend on that they have to change their upgrade timescales to suit mine? Even if I had enough time to help them all meet that kind of timescale, why would they agree to fit their changes into my required deadline? Maintainers are under a lot of pressure. Having users come along and say "we'll add 50 developers to your project if…
You shouldn't take "Do you have programmers?" too literally.
Programmers ~= Resources ~= Money
=> If you want your dependencies to be upgraded in a reasonable time frame, try to contribute to financing the maintainers (or support them in a manner _they_ find suitable).
Re: Sunsetting Python 2
#245> If people find catastrophic security problems in Python 2, or in software written in Python 2, then volunteers will not help you. If you need help with Python 2 software, then volunteers will not help you. Well, isn't it the benefit of FOSS, that volunteers can, and in the case of such a critical piece, so much used as Python 2, in all probability will, step up. Doesn't have to be the same people as the core team i…
Exactly! I am getting tired of FOSS orgs thinking they can speak for their entire extended community. `PSF` should be inserted before every occurance of the word volunteer in that page.
They're announcing that the (small group of) people developing the Python2 executable are no longer going to do so after Jan 1st.
In what way does this imply that they're speaking for any "extended community"? Who're you trying to say is being mistaken here as being a "volunteer" but is not a 'PSF volunteer".
I totally get that there is an "extended community" around the Python language(s), including at least module authors, people who write Python frameworks, and people who write code in Python - and _possibly_ including devs at companies who have built products in Python or relying on Python. But it's 100% obvious that the linked article is referring to none of those people.
Who do you think this "FOSS org" was appropriately speaking for?
Re: Sunsetting Python 2
#246Is there even a plan to transition the chromium code base to python3?
Re: Sunsetting Python 2
#247I 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/
Is Manjaro included in that?
Edit: Yes Manjaro has default Python3 too. :)
Re: Sunsetting Python 2
#248Some shared hosting providers are still offering Python 2.6 as their main offering.[1] Optionally, there's Python 3.2, probably the worst 3.x version. [1] https://www.hostgator.com/help/article/what-software-and-pro...
I bet there is still some shitty hosting company somewhere offering Perl4 CGI script hosting.
Doesn't mean we should do anything except laugh at their incompetence (or perhaps be impressed by their ability to monetise other people's incompetence...)
Re: Sunsetting Python 2
#249People spend more time whining about the transition than it would take to do the actual transition. Sigh.
Re: Sunsetting Python 2
#250Python 2 to 3 (at least by 3.3 or so) was one of the easiest transitions I've ever done. There's a library ("six") to help, and in almost all cases you can write 2-and-3 compatible code, which means you can go piece-by-piece. (Unless your manager makes drive-by commits of py2-only code, months after you all agreed that all new code should be py3-compatible, and then leaves town for a multi-week vacation...) Dependenc…
> If we switched from phillips to torx, and your favorite tool brand didn't make torx drivers yet, you've got to either convince them to start, or switch brands.
This is the best analogy I have yet read. Thanks - you nailed an argument I have had at multiple gigs/clients way to often.
> Professionals don't get to use this as an excuse to badmouth torx, and stick with phillips.
D'accord. Exactly. I had very fruitful discussions with professional builders about tools, tool brands and their respective strengths and weaknesses - but never has a professional decried Bosch Pro vs Makita vs DeWalt. One has ones favorites - and that is fine. But badmouthing - I have never encountered.