Hey, Could we at least get the hacked sage-sync-build into 5.10? The combinat queue has a few patch which create new cython files that replace python files (i.e. cythonizes them) which requires the sync-build to be run when people are moving ahead of those patches. Rebuilding all cython files in sage seems like a high price to me for something we can put a quick patch (no pun intended) over.
Thanks, Travis On Sunday, June 2, 2013 3:32:12 AM UTC-7, leif wrote: > > leif wrote: > >> leif wrote: > >>> 4) Minimally adapt sage-sync-build.py to reflect the (hard-coded) > change > >>> by #14570. [May be easy as well, but potentially unsafe.] > > > > Even that turns out to be non-trivial, AFAICS, i.e., the whole strategy > > would have to get changed, as opposed to just some file / directory > > names in a few places. > > Just for the record: > > I've meanwhile managed to hack sage-sync-build.py such that it > /seems/^TM to work with a Cython build_dir (below $SAGE_SRC/build/) as > well, but the patch would need clean-up and thorough testing. > > And as mentioned, the script needs further, not directly related, fixes > anyway, so I'd prefer to postpone changes to sage-sync-build to 5.11. > > > -leif > > -- > () The ASCII Ribbon Campaign > /\ Help Cure HTML E-Mail > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
