News for hackers. Stuff that matters.

A comment on What Killed Perl?. Parent comment

Re:What Killed Perl? by mixmastamyk on Wednesday November 19, 2025 @02:42PM (#45984114)
I was not affected by Py3 at all. First I completely ignored it for five years while it gestated. Then started kicking the tires when 3.4 dropped on a LTS. When 3.6 with better dicts and f-strings landed I moved over with barely a whimper, since I'd had a decade to get things upgraded to 2.7 first.

None of my projects needed to worry much about char encoding, and I used logging extensively starting under 2.6 or so.

[ Parent | on HN ]
Re:What Killed Perl? by selcuka on Wednesday November 19, 2025 @07:03PM (#45987039)
Porting your own code was relatively easy. The problem was porting all your dependencies, and replacing the ones that were abandoned and didn't support 3.x.
[ Parent | on HN ]
Re:What Killed Perl? by mixmastamyk on Wednesday November 19, 2025 @08:14PM (#45987574)
I did wait a bit for Django and SQLAlchemy but it wasn't long, they may have been ready for 3.6. Small deps were replaced or eliminated.
[ Parent | on HN ]
Re:What Killed Perl? by masklinn on Thursday November 20, 2025 @02:40AM (#45989995)
They were ready long before 3.6, sqlalchemy added support for Python 3.1 in 0.6, and Django 1.5 introduced support for Python 3.2 on an experimental basis with 1.6 removing the “experimental” bit.
[ Parent | on HN ]