On Thu, Jan 31, 2013 at 7:29 PM, Keshav Kini <keshav.k...@gmail.com> wrote:
> Dima Pasechnik <dimp...@gmail.com> writes:
>
>> On 2013-01-31, Keshav Kini <keshav.k...@gmail.com> wrote:
>>> Dima Pasechnik <dimp...@gmail.com> writes:
>>>> On 2013-01-23, Robert Bradshaw <rober...@math.washington.edu> wrote:
>>>>> On Tue, Jan 22, 2013 at 9:53 PM, tom d <sdent...@gmail.com> wrote:
>>>>>> Another possible solution would be to change the error message one gets 
>>>>>> on a
>>>>>> failed import statement.  (I also lost hair on this issue a couple days
>>>>>> ago.)  Right now it says 'have you tried %upgrade?' or something 
>>>>>> similar; it
>>>>>> could include the recommendation to -sync-build.
>>>>>
>>>>> +1 to this idea, -1 to making ./sage -b take longer.
>>>>
>>>> couldn't we just call sage -sync-build automatically, if importing
>>>> fails?
>>>> (with a proper message, of course)
>>>> Or is it going to mess things up in some cases?
>>>
>>> Isn't the problem that importing succeeds when it shouldn't? How can we
>>> detect that?
>> well, I read that people don't want sage -sync-build to be called from
>> sage -b, as it takes extra few seconds. I'm just saying "OK, if this is
>> the only issue, why can't we do this only if something goes wrong?"
>
> 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...)

- Robert

-- 
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.


Reply via email to