Why Python is Important for You

Re:Why Python is Important for You by anthonyb on Saturday February 11, 2012 @04:29PM (#3580230)

The way I would do it is to push the processing out to functions, too. Something like:

  verdict = get_verdict(the_thing)
  if verdict not in blessedsolutions:
      return

I'd advise against running returns onto the same line - I find it makes it harder to read, particularly when you have a lot of checks like this.

[ Parent | on HN ]

Re:Why Python is Important for You by Luyt on Saturday February 11, 2012 @04:37PM (#3580251)

"The way I would do it is to push the processing out to functions, too."

This is indeed a good idea to isolate code away, but wouldn't alleviate a deeply nested control structure. It would make it somewhat more easier to look at, though.

"I'd advise against running returns onto the same line "

I usually follow PEP8 and place returns and continues on the next line, but the code examples I posted earlier had to be a bit condensed to conserve screen space, that's why ;-)

[ Parent | on HN ]

Re:Why Python is Important for You by anthonyb on Saturday February 11, 2012 @09:58PM (#3580965)

Sometimes your problem space is really just that complex, in which case there's not much you can do, short of writing some sort of business rules engine.

[ Parent | on HN ]