> Robert wrote: > > I've done a few more tests on Linux and Win, and it does so far on > my side in all modes - for practical edit-run/reload debugging > purposes. The reload_support=False is anyway default. > > the little 3+.patch in attachment in addition to pyxi3.patch > http://trac.cython.org/cython_trac/ticket/312 > (or manually against 0.11.1) > finally would solve the mentioned "reload(my) -> ImportError: No > module named my" problem of 0.11.1 or of reload_support=False > default mode > > I leave it open so far from my side.
Thanks. I wanted to discuss some things a bit more, which is why it didn§t make it. The thing is that when a new format is introduced (pyxbld in this case), we have to make sure it is the right one because once it's there we must be backwards compatible. In my opinion, pyximport is for the "simple cases" where you do not really want a build system. The pyxbld file however is verbose enough that one might perhaps as well write a setup.py...or have pyximport invoke a setup.py... One thing I was thinking about is embedding the information in the pyx file itself. Something like this perhaps: from cython import pyxbuild pyxbuild.include_path = [...] pyxbuild.libraries = [...] .. rest of pyx file... What do you think? Dag Sverre _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
