Yeah, the very strange this is that __package__ (in that code in
Importer.cs) is done BEFORE the module is even loaded. I don't see how it
could be ever setting the __package__ attribute correctly. In CPython,
import.c is about as "confusing" as Importer.cs, so at least IP is
compatible with CPytho
It happens in Importer.cs - there's a comment saying "// explicit relative
import, calculate and store __package__"
It also happens in imp.new_module, when creating the sys module, and in
PythonContext.CreateBuiltinModule, but I think those are all much less
interesting.
Import bugs are really
