#4480: [with new patch, needs review] cython dependancy checking is too slow
----------------------+-----------------------------------------------------
 Reporter:  robertwb  |        Owner:  craigcitro
     Type:  defect    |       Status:  assigned  
 Priority:  major     |    Milestone:  sage-3.2.1
Component:  build     |   Resolution:            
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by craigcitro):

 * cc: tornaria (added)
  * owner:  mabshoff => craigcitro
  * status:  new => assigned
  * summary:  [with patch, under review] cython dependancy checking is too
              slow => [with new patch, needs review] cython
              dependancy checking is too slow

Comment:

 Here we go! So this patch applies on top of `rc0` + the patch at #4500,
 because it was a needed fix. With this patch in, we've got it all: fast
 cached dependency checking, parallel calls to Cython, and dozens of small
 improvements to the build system thrown in, too. I also reorganized
 `setup.py` and created a `module_list.py` to have the list of extension
 modules.

 Robert, I've looked at (probably every line of) your code which is now in
 here -- can you review the rest? I did make small changes to one or two of
 your functions; in particular, `parse_deps`, I think.

 I've run it through some paces, but I'm happy to fix any bugs that pop up.

 Credit should go to Rob, Gonzalo, and me.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4480#comment:2>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to