News for hackers. Stuff that matters.
Re:Bash $* and $@ (2017) by acdha on Sunday January 12, 2020 @07:44PM (#22030916)
I haven't really found that to be a problem, with some code I still use daily which was started before Python 3.0 was released. The py3 transition was real but it was also something which took seconds to run through futurize/modernize.

Over the years I've spent way more time going into inconsistencies about the various platform tools (e.g. GNU vs. BSD implementations of sed, grep, find, etc. even before you ge to the space aliens-with-broken-translators realm of AIX) — which using Python avoided needing to care about — or library / file naming changes. Similarly, a few years back there was way more time used when various HTTPS improvements flushed out code using old versions of OpenSSL or, worse, gnutls.

Re:Bash $* and $@ (2017) by scbrg on Monday January 13, 2020 @05:51AM (#22033362)
I'm glad you mentioned SSL. Because hey - that broke some scripts in 2.7.9 ;-)

https://www.python.org/dev/peps/pep-0466/

(Can't remember the details, but it may have been something about some extra hoop you'd have to jump through to trust self signed certs that broke our testing infrastructure)

Re:Bash $* and $@ (2017) by acdha on Monday January 13, 2020 @09:24AM (#22034663)
Totally agree - I just don’t see that as a distinguishing factor since we had a bunch of shell scripts break, too, as various CLI tools stopped behaving consistently.
Re:Bash $* and $@ (2017) by scbrg on Monday January 13, 2020 @09:35AM (#22034760)
I guess this is a YMMV thing. My experience is that Python rots more than shell scripts, but of course I understand that this may not be universally true, and depends a lot on what your scripts actually do (and, to a large extent, on how they're written, of course).