Linked by Thom Holwerda on Fri 10th Sep 2010 14:59 UTC
General Development Python programmers shouldn't get too smug. While many people agree that Python is designed in a way that makes it a highly readable language, there can still be problems with legacy, untested Python code too. Porting legacy Perl to Python can be a daunting task. In this article, learn some of the theory behind dealing with legacy code, including what not to do.
Thread beginning with comment 440353
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Why would I want to do it?
by sreque on Fri 10th Sep 2010 18:35 UTC in reply to "RE: Why would I want to do it?"
Member since:

We managed to compile Python 2.6 on an AIX 5.2 server without incident. Perl does have an advantage here, but it's only really an advantage when you are distributing scripts to customers that have no interest in installing Python on their servers, and I believe this case is very rare.

Reply Parent Score: 1

Bill Shooter of Bul Member since:

Well, I occasionally help out friends maintain their websites. Which means I log into random shared hosting boxes, whos OS and software installed I can't control. Often times, there are batch operations that I could fix easily with a script. I can't count on python always being there, but perl is always there.

Reply Parent Score: 2