This occurs when attempting to manually use the py discover module directly (not through the PikeManager). I haven't discovered exactly why it happens, but it seems to have something to do with treating the immediate children of the specified module as packages instead of independent modules. More investigation needed.