Testing for ImportErrors in Python -


We are making real problems with those people who are checking in code that does not work because something is re- Of course, this is partly because our developers do not really have any good tools to easily find these types of mistakes.

Is there any device to help you find imported errors in Python? Of course, the correct answer is here "You should use your unit test for this." But, I'm in heritage code land (at least according to the definition of Michael Wing), so our unit tests are doing a great job on us.

In the meantime, the tool must walk through each directory and import each file, in which any scripts will be imported into imported eaters (such as file or class recently changed) Search for I think it would not be difficult to write to myself, but is there any such program that has already been written to do this?

Pikeker imports this module for you and receives these errors.

Oh, and "Pilint & lt; Modulamam" The module will import, but I think you have to call it once for every module, where at least supports *. (Pylint also supports * .p but in that case the module will not import).


Comments

Popular posts from this blog

c++ - Linux and clipboard -

Visual Studio 2005: How to speed up builds when a VSMDI is open? -

booting ubuntu from usb using virtualbox -