[Eric] Prevent debugger from stepping into empty __init__.py files

[Detlev Offenbach]

On Sonntag, 8. Februar 2009, Geert Vancompernolle wrote:
> Hi,
>
> Is it possible with Eric4 to prevent stepping in (mostly) empty
> __init__.py files while debugging?  The annoying think is that the file
> is opened and that makes the tabs view on top of the editor
> unnecessarily more crowded.
>
> Preventing opening the __init__.py files would enlighten the sometimes
> very crowded tab line on top of the editor.
>
> One could first check if the file is really empty (because sometimes you
> /want/ to put something into that file).  If it is, skip it.  If it
> isn't, step through it (if that is at all relevant, of course...).
>
> Could also be a preference option...

How did you stop at an empty __init__.py file? If you are executing a script 
step by step (using the relevant actions), every file stepped into will be 
shown and execution will stop there. That can be changed if one uses the step 
over instead of the step into action.

That said, the observed behavior should be normal, if the __init__.py file 
contains executable code. If it is completely empty, it shouldn't be opened 
because there is no statement for the debugger to stop at.

Regards,
Detlev
-- 
Detlev Offenbach
detlev at die-offenbachs.de