On Thu, Feb 5, 2009 at 1:51 PM, <[email protected]> wrote: > That's usually done by the C API already. pygame's current __init__.py > however hides nearly all import errors and sets up some lambda expressions > that cause code to fail badly in case the module could not be imported > correctly. To fix the import issue, the initialisation system has to be > fixed > first. > > Yeah, what's up with that __init__.py anyways?
why would it want to hide a failure to import pygame.surface and instead make it an error on calling pygame.Surface? Is there anybody who actually uses pygame in a situation where the .surface module is not available? Was there ever any real world case where somebody was having "import pygame" fail on them because pygame.surface could not be imported, and they actually wanted to ignore the pygame.surface import failure? cause if there's no practical purpose to it, the try block around the __init__.py imports should be removed so the actual import exceptions can be seen.
