Changes between Initial Version and Version 1 of Ticket #21480, comment 129


Ignore:
Timestamp:
09/29/16 15:53:29 (3 years ago)
Author:
embray
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21480, comment 129

    initial v1  
    1 I would disagree.  In fact as the discussion in #20730 demonstrates that writing a technically correct makefile for this case results in a makefile that's "too complicated to understand".  I can do this correctly in Python with about the same amount of code it takes to invoke make as a subprocess (which is also pretty non-standard to do anything in a Python setup).
     1I would disagree.  In fact as the discussion in #20730 demonstrates that writing a technically correct makefile for this case results in a makefile that's "too complicated to understand".  I can do this correctly in Python with about the same amount of code it takes to invoke make as a subprocess (which is also pretty non-standard to do anything in a Python setup). Not to mention the contents of the Makefile itself (no matter how "correct" it is).
     2
     3Part of the idea is also not to make non-Sage developers blanche when they look inside of sage's setup.py.