This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients jftuga, rhettinger, vstinner
Date 2015-08-20.22:47:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440110840.65.0.395327545111.issue24904@psf.upfronthosting.co.za>
In-reply-to
Content
In general, it isn't good design to incorporate timeout logic in computation logic.  What would be better is a general purpose, reusable, decoupled tool: run_with_time_limit(some_computation, some_args, time_limit).  Such a tool might be based on separate process that can be timed or killed, it might use signals, or may be based on threading.Timer.

I did a quick look around the net.  Timeouts on diff APIs aren't common (i.e GNU diff doesn't have a timeout) but there are a couple of precedents (you aren't the first to have had concerns about the running time for unfavorable inputs).
History
Date User Action Args
2015-08-20 22:47:20rhettingersetrecipients: + rhettinger, vstinner, jftuga
2015-08-20 22:47:20rhettingersetmessageid: <1440110840.65.0.395327545111.issue24904@psf.upfronthosting.co.za>
2015-08-20 22:47:20rhettingerlinkissue24904 messages
2015-08-20 22:47:20rhettingercreate