On Thu, Jun 11, 2009 at 12:40 PM, Stefan Behnel<[email protected]> wrote: > > Lisandro Dalcin wrote: >> On Thu, Jun 11, 2009 at 2:31 PM, Ondrej Certik<[email protected]> wrote: >>> As far as Cython is concerned, the only problem I can see is that it >>> changes all import paths to the fully qualified import paths. Python >>> allows both ways, Cython only the fully qualified way. As Stefan >>> explained, this is needed, because it will then not work properly at >>> the moment. But I am not convinced this cannot be fixed -- though it >>> may happen that the fix is too tedious and not worthy. >>> >> >> IMHO, the only "fix" Cython needs is support for relative imports... >> Then you could write: >> >> from ._hermes2d cimport what_you_need >> >> This way, Ondrej would be able to easily write Cython code using >> relative imports the right way... > > I thought about this, too, and yes, that would be a nice feature. But it > doesn't help in this case. What Ondrej wanted was to be able to import the > module both from its package and as a plain import, i.e. when put outside > of any package. The above would not handle the latter case either.
I think it would. I have _forms.so and _hermes2d.so. The _hermes2d.so is imported from _forms.so and if the import was relative, e.g. if _forms.so was doing "import ._hermes2d", then it should work both in the tree and out of the tree. Ondrej Ondrej _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
