<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">> It's also consistent with Python that classes, such as those in<br>
> Cython.Compiler, can have their methods overridden through class<br>
> inheritance.<br>
<br>
</div>That's a good idea, we should totally allow that for the next release. ;)</blockquote><div><br>Which is when, if you're being serious?<br><br>I ask because we arrived at the conclusion that it'd be much easier to branch Cython with the changes we need rather than inherit and override. We're discussion now how we're going to tackle this, and there's a pretty clear consensus that we want to finish this for the next release for later this month, one way or another.<br>
<br>Whether you guys plan Cython to continue insisting projects using it to have a similar structure as Sage directly impacts this discussion.<br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Depends on how you do it. Do you use distutils or call Cython by hand?</blockquote><div><br>We're not using Cython right now, until a workaround or alternative is setup it's not an option.<br><br>We are currently "from Pyrex.Compiler import Main" which runs through roughly 100 lines of code to detect whether any source files have been modified since the .c file for it was last generated (and regenerating dependencies when a .pxd is modified), along with some OS-specific code handling library name conversions and OSX frameworks.<br>
<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
BTW, "a few pesky bugs" was referring to your code and build setup, not<br>
Cython, right?</blockquote><br>Consider that one man's feature is another man's bug.<br><br>Our source layout is setup to make development easier<br><br>Our Python API design is to make coding with it simpler<br>
</div><br>Having to compromise one or both in order to use Cython is a bug to us. If I had my way, the Distutils would handle these source files the same way it handles .c source files - specifying which sources need to be linked each extension. Our current method of .pyx files filled with include statements for .pxi files in the same directory is a workaround for Pyrex's lack of this functionality.<br>
<br>No hostility intended, just expressing viewpoint.<br>