You clearly aren't running extensive production systems with little administrative resources. Code is written 15 years ago, and it's still running. Any changes that break something are major headache, usually leading rolling things back to working version. Nobody knows or cares to fix those things to achieve compatibility with new version. This leads to situation where nothing at all is ever updated. And even known bugs and exploits aren't getting fixed. Oh well, that's business as usual.
But when I'm writing new code, I'm of course using Python 3.
> But when I'm writing new code, I'm of course using Python 3.
There's no "of course" about it, which is the point of the article. It is interesting that you're using Python3. It means that you're not blocked by library availability (public or company-internal). It means that you are permitted by management to use it. It probably means that you prefer it.
My situation is different on the last two points, but I am also not blocked by library availability.
But when I'm writing new code, I'm of course using Python 3.