Not all C/C++ sources are auto-generated from Cython files. Some extension
modules in Sage use hand-written C/C++ source as well. If we litter the
cythonize output into the source tree (and cross our fingers that there is
no name collision with a hand-written C/C++ file) then it is potentially
Thanks for the clarification.
Not all C/C++ sources are auto-generated from Cython files. Some extension
modules in Sage use hand-written C/C++ source as well. If we litter the
cythonize output into the source tree (and cross our fingers that there is
no name collision with a hand-written C/C++
Putting files of interest in different directories is also confusing.
I, personally, prefer the .c(pp) files co-existing with the .pyx ones.
I think it's pretty standard to have a single source tree have mixed
source and compiler output during development--this goes back to the
make vs make
On Saturday, July 5, 2014 8:50:38 PM UTC-4, Robert Bradshaw wrote:
I, personally, prefer the .c(pp) files co-existing with the .pyx ones.
Well as I said, there is more than one way of doing things. But I do
believe that VPATH builds become more useful the larger the project grows.
Once you
On Sat, Jul 5, 2014 at 8:17 PM, Volker Braun vbraun.n...@gmail.com wrote:
On Saturday, July 5, 2014 8:50:38 PM UTC-4, Robert Bradshaw wrote:
I, personally, prefer the .c(pp) files co-existing with the .pyx ones.
Well as I said, there is more than one way of doing things. But I do believe
Relevant ticket: http://trac.sagemath.org/ticket/14570
On Sunday, July 6, 2014 12:11:46 AM UTC-4, William wrote:
On Sat, Jul 5, 2014 at 8:17 PM, Volker Braun vbrau...@gmail.com
javascript: wrote:
On Saturday, July 5, 2014 8:50:38 PM UTC-4, Robert Bradshaw wrote:
I, personally, prefer
On Sat, Jul 5, 2014 at 9:15 PM, Volker Braun vbraun.n...@gmail.com wrote:
Relevant ticket: http://trac.sagemath.org/ticket/14570
Thanks: my understanding having read that is that a year ago during
the git transition, this change was basically an optimization Andrew
Ohana wanted to make (1) using
