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 440377
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 sigzero on Fri 10th Sep 2010 21:31 UTC in reply to "RE: Why would I want to do it?"
sigzero
Member since:
2006-01-03

You are really trying to say that Pythons package/module system excels over Perl? Really?

Most of those are pure FUD.

Reply Parent Score: 4

sreque Member since:
2010-09-10

Yes, because a flat namespace, an overly complex system for importing and exporting of symbols, stapled-on OO, and requiring you to put a non-zero-returning statement at the end of each file makes for an excellent package system.

It's only FUD if you're biased for Perl! For the rest of us, it's the truth.

Edited 2010-09-15 16:29 UTC

Reply Parent Score: 1