[Grinnz]

Curious what makes you think Python will be less susceptible to this, after the whole 2to3 debacle?

I'll note that Perl just went through a year or so of painful argument to rediscover that "Perl should stay Perl", so I'd be more confident in that.

[hedora]

This. Perl at least attempts to maintain backwards compatibility. Python libraries and the interpreter actively break old code all the time.

Also, Python is at least as bad as Perl about breaking silently. If you care about maintaining a codebase over time, pick anything that has static types.

I’ve found Go to be a reasonable python replacement, though I haven’t found either python or go to be a reasonable perl replacement.

[dave_aiello]

I don't know. I felt that Python 3 was an attempt to route around problems in Python 2 that couldn't be easily fixed.

I don't have much invested in Python at the moment. I would be more aware of and concerned about Python issues if I had larger scripts written in it that I need to maintain.

I have used Perl 5 long enough to know that it is a mature language. I'm concerned about the integrity of CPAN and individual modules' abilities to interoperate with the versions of Linux that I deploy in production.