8 ms·
How Is Python 2 Supported in Red Hat Enterprise Linux After 2020?
- tick_tock_tick 7y agoWhile you should move on to python3 at this point I still stand by the whole thing was a giant waste of time. 'Better' unicode support was not worth the mess. Everything else could have been done in python2.
- MereInterest 7y agoThat's only if you are dealing with an US English userbase who never copy/paste from Microsoft Word. Anything else, and the better unicode support is a godsend. Better have them pop up as type errors during development than as uncaught exceptions whenever a user happens to first put unicode somewhere you don't expect.
- dr_zoidberg 7y agoNot just non-US users, but also emojis.
- kissgyorgy 7y agoYour package build probably never broke because you have an accented character in your name...
- tick_tock_tick 7y agoI limit all my non-ascii to comments. The tooling just isn't there to support it.
- kissgyorgy 7y agoPython2 was not there to support it. Python3 is fine.
- ASalazarMX 7y agoI strongly disagree: decoding and recoding strings to-from UTF8 was a monumental waste of time IMO. Never has one language gave so much trouble for simple tasks like reading a database. Python3 just works seamlessly.
- loeg 7y agoImplementation details of u"" could be changed without rototilling the language. Breaking the print statement does not improve unicode support, for example.
- airstrike 7y agoThe change to the print statement is an absolutely trivial for any project. Literally all you have to do is type in "2to3 foo.py". Boom, done.
- takeda 7y agoAll the people that are crying about print() never did any migration. That's the easiest part, it can be fully automated. In fact you will almost never use print in any serious program. The unicode is the most difficult part of the migration, because most of python 2 code is actually broken, it can't be automated because you need to know what you want whether you need text or bytes.
- jzwinck 7y agoIn Python 3 if you have bytes and write them out using the "csv" module, you get something like this: b'A',b'B' b'1',b'2' That's not seamless, and I wouldn't say it helps non-English speakers either. This bug impacts Pandas to_csv as well.
- deleted 7y ago[deleted]
- agoodthrowaway 7y agoSorry but I don’t agree this is a bug. You need to decode your bytes to properly write a string. Otherwise you get the unexpected result you are showing because it has no way of knowing how your bytes are encoded.
- etaioinshrdlu 7y agoI think in hindsight v3 mode could be enabled per file, rather than per program. That wasn't done, but for reasons that amount to "we don't want to"... I simply believe the python authors made the wrong choice.
- joshuamorton 7y ago> That wasn't done, but for reasons that amount to "we don't want to"... Well, and giant glaring differences in internals. Python3 and python2 have incompatible bytecodes. Swapping compilers on a per-file basis in a language as dynamic as python isn't possible. Python allows dynamic re-writing of modules and source code. How do you decide which version a module is run with if the module is modified at runtime?
- chc 7y agoIf you made all the other changes but still called it Python 2, how would that help anything? You're still making the same breaking changes. And if you're not talking about making all the same changes...then it doesn't sound like everything else could have been done in Python 2.
- Havoc 7y agoI get that enterprise-y stuff is on a more LTS slow schedule, but: Python 3 was released a DECADE ago - literally. If you've got mission critical stuff running on Python 2 and are panicking now then it's time re-evaluate your life choices.
- devnonymous 7y agoNot that I'm against python 3 but please, this dismissive arrogant attitude says more about your experience with python than of people who took their time. Python until at least 3.4 was changing way too fast to be considered as a stable platform to port to. The actual window for migration has been more like 3-5 years. Yes this has been sufficient but not so long that people need to question their life choices for being cautions.
- Havoc 7y ago>The actual window for migration has been more like 3-5 years. Fair - the 2-->3 transition was indeed painful. So 3-5 years actual migration window, with advance notice of "Python3 is coming of another 7-5 years". Whichever way you look at it - that's a decade advance notice. In a industry that moves exceptionally fast. If you want to judge me as "dismissive arrogant attitude" for that - so be it. >people need to question their life choices for being cautions. The life choices phrasing was a poor choice on my part & I apologize for that. Message is unchanged though. To me waiting till support window runs out and then thinking of next step is the exact opposite of "being cautious".
- kortilla 7y ago>and then thinking of next step is the exact opposite of "being cautious". I don’t think you fully grok the risk of code changes in some of these large legacy systems. EOL with no security patches on a closed system that processes trusted inputs is nearly 0-risk.
- Havoc 7y ago>fully grok the risk Oh I get the risk. What I don't get is someone sitting on this for a decade and at EOL starting to wonder how this is gonna work. >nearly 0-risk That's cool to. I mean there are *nix servers with years of uptime that haven't seen a proper update since ever. All good (sorta). I coded in Python 2 last week - nothing against it. It's the bizarre "this decade long transition just snuck up on us" tone of the question that gets me.
- baylisscg 7y agoTellingly they go out of their way to say security fixes are always at their discretion and come from upstream. After explaining that a no feature updates is fine as upstream will be effectively dead. This ain’t Python’s problem Red Hat this has been slated for years
- tingletech 7y agoI've some good luck migrating a couple of things to `pypy`, specifically "Squeaky's portable Linux binaries." [0] "How long will PyPy support Python2? -- Since RPython is built on top of Python2 and that is extremely unlikely to change, the Python2 version of PyPy will be around “forever”, i.e. as long as PyPy itself is around." [1] [0] https://github.com/squeaky-pl/portable-pypy#portable-pypy-distribution-for-linux https://github.com/squeaky-pl/portable-pypy#portable-pypy-di... [1] http://doc.pypy.org/en/latest/faq.html#how-long-will-pypy-support-python2 http://doc.pypy.org/en/latest/faq.html#how-long-will-pypy-su...
- geofft 7y agoI mean, it's not like CPython 2 is going to disappear on January 1, either. You can keep using it. What you lose is a) potential security fixes (you might not care, for your use case) and b) the ability to use other libraries that are Python 3 only, including security updates to libraries whose Python 2 versions are no longer maintained. Using PyPy (or any other Python 2 implementation) definitely doesn't get you b and arguably isn't much improvement on a.
- ggm 7y agoGiven what people pay RH for, this makes sense. Given why people like me no longer choose to run RH, this makes perfect sense, as a reason why we don't run RH: The money we pay RH to maintain support for old code can be better invested in converting old code to run on new platforms. There is a class of client who needs what RH is selling and I am glad they sell it, and that people like my bank can invest in that, because longterm stability of fintech cores for a banking product is very important: People ran applications developed for LEO, in emulation under GEORGE and then subsequently re-emulated on later operating systems because ICL committed to that to meet customer needs. People emulated PDP-11 RSTS inside Vax/VMS for the same reason. People emulate OS360 inside RS6000 based machines.. TL;DR RH supporting Python2 makes perfect sense. If you don't use RH, then this doesn't have to matter to you.
- colechristensen 7y agoOpposite position: The money you pay supporting security and new/broken features of fast moving upstream targets could be mostly saved with a small portion paid to RH freeing you up to improve your product instead of supporting ever-changing/insecure upstreams. I have experienced far too many emergencies and worried about relying on far too much insecure old code in environments without RH support. With RH I could always trust that packages wouldn't disappear overnight, if I built something against RH it would actually still be there in 6m or 6y and that I could really trust that if a security hole was discovered I would be notified and it would be fixed in a way that wouldn't break my stack. All of that is super valuable compared to moving fast and breaking things myself while dealing with upstreams that move fast and break things too. In many many circumstances, it is really expensive to stay on the bleeding edge of everything and does not add business value, other than pleasing and attracting magpie programmers.
- takeda 7y agoI worked for a company which paid for RH licenses (they don't do it anymore). Being conservative is nice, if it comes with stability, but during RHEL6, 6.4 was the first version that was actually stable. As for breaking your stack, this actually is not that hard. All you have to do is not tie your application to the system. Since we're talking about Python, if you use RedHat or CentOS, I highly recommend IUS repo[1] in there you can pick which version of Python you want to use (older if you want to ensure stability, newer if you need cutting edge), you also can install multiple versions side by side, and your application is no longer tied to the OS, that means switching underlying OS or upgrading to next major version (for example to RHEL8) is no longer that should affect your application. [1] https://ius.io https://ius.io
- poppabox 7y agoI was hoping this would be a two word website that just said "It's not" in <h1>
- djsumdog 7y agoI really wish these big bulky enterprise and commercial solutions wouldn't prop up this technical debt. Things like ArcGIS an other $10k+ software packages have built in Python2 interpreters. If all of them decide to keep "supporting" py2, a ton of security updates are going to fall through the cracks or become non-uniform across tools. They've literally had years and years to upgrade their tooling. But considering some of this enterprise crap still has support for VBA (Visual Basic for Applications) we'll probably see Python2 in the wild well into 2030. Makes you wonder how much COBOL is still out there.
- crygin 7y agoAs an alternative viewpoint, it's bizarre that we can't support these things. Mathematics textbooks from 400 years ago are relatively intelligible, and those from 100 years ago are easily readable. But with computer science, a domain which consists entirely of problems we ourselves invented, we've wedged ourselves into a situation where we are apparently so bad at computer language design (let alone systems engineering/systems architecture) that something surviving for a decade is frankly notable.
- gtirloni 7y agoProgramming languages are more like spoken languages than mathematical languages. They evolve fast. Programming languages also are versioned, something that's nonexistent and blurry in spoken languages. There's no support for Latin in almost any software today and books in Latin can be read by a extremely small minority. Even a English speaker from the 1700s would have trouble with today's English.
- zamadatix 7y agoApples to oranges. I don't think you'd be as surprised if the statement were reworded to "the human brain has more flexibility in parsing to understand intent from text than a computer". The issue is very unlikely to be poor language design as, as you allude, people can parse old code just fine. The thing we're actually bad at is building computers that reason intent from content like we do.
- 7y ago
- potatofarmer45 7y agoFor a large deployment of our SaaS software last year, in order to connect to the raw data for their POS, we discovered they were on mainframes running UNIX. Not Linux, Unix. We had to go to a local library, in the old archived basement to find books that guided us on what the hell we were doing. 50 years from now, with new completely different languages being vogue, some poor engineer is going to have to find a book for Python2.
- keyle 7y agoFun story :) On the plus side, the Python2 will probably not look that different from Python6 :)
- potatofarmer45 7y agoI'm sure by then there'll be brainwave controlled programming and the idea of using a keyboard with defined syntaxes will be as silly as punching cards sound to us today haha
- beatgammit 7y agoThere are plenty of Unix systems out there, such as AIX (and arguably FreeBSD, though it's not certified), that are derived from and could be called UNIX. These systems are still maintained today and generally have the philosophy of "if it ain't broke, don't fix it". And there's definitely some sense in that, and I wish more software projects followed that philosophy. If you take C code from K&R C, it'll likely still compile with current C compilers. Likewise, I'm sure most C projects from the 80s still compile with current compilers, perhaps with minor changes. FreeBSD often chooses to improve existing tools instead of replacing them, so it would look more familiar to an old Unix expert than Linux, and there's some solid logic to that. I think it's a little sad that we have these big disruptive changes like Python 2 -> 3, when Python 2 still works fine and can still be improved without breaking backwards compatibility. Honestly, I think it makes sense to have disruptive changes like that be treated as a new language instead of completely dropping support. I like how the Rest project is approaching it with building compatibility for older versions of the language into current compilers, so you can get the best of backwards compat and modern changes.