Robert Bradshaw <rober...@math.washington.edu> writes: > On Thu, Jan 31, 2013 at 7:29 PM, Keshav Kini <keshav.k...@gmail.com> wrote: >> But an import statement succeeding when it shouldn't *is* something >> going wrong - it is exactly the kind of problem which is caused by not >> doing `sage --sync-build` after running `sage -b`. >> >> By the way, another issue is that `sage --sync-build` is documented >> neither in `sage --help` nor in `sage --advanced`. See >> http://trac.sagemath.org/sage_trac/ticket/14046 . > > On this note, weren't we planning on moving to a more of a "distutils > develop" model rather than having to have an extra build step and > directory in the long run? (Of course a command would still be needed > for re-compiling Cython code...)
Indeed. The trac ticket is here: http://trac.sagemath.org/sage_trac/ticket/12659 See also http://trac.sagemath.org/sage_trac/ticket/13190 . -Keshav -- 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.
