On Wed, May 29, 2019 at 2:12 AM Colby Kelln <cke...@umich.edu> wrote:
>
> Hi,
>
> I'm receiving a similar error message. What exactly did you do to fix the
> problem?
it depends - try starting sage, and post the error message (and
probably the relevant logs, too) here.
I wonder whether changing the way sagenb dependencies are dealt with
might make this error handling more robust.
>
> Thanks
>
> On Sunday, April 21, 2019 at 10:30:49 AM UTC-4, vdelecroix wrote:
>>
>> Indeed, sage did not start... After fixing it, sagenb installs.
>>
>> The error message is really confusing.
>>
>> Le 21/04/2019 à 16:25, Dima Pasechnik a écrit :
>> > this error is an indication of an earlier build error. Try starting sage.
>> >
>> > On Sun, 21 Apr 2019 15:13 Vincent Delecroix, <20100.d...@gmail.com>
>> > wrote:
>> >
>> >> Ignore the second e-mail: the error occurred again compiling
>> >> from scratch.
>> >>
>> >> Le 21/04/2019 à 14:24, Vincent Delecroix a écrit :
>> >>> It appears to be a problem with my setup.
>> >>>
>> >>> I had some Python libraries in my $HOME/.sage/local
>> >>> that made interference with the sage installation.
>> >>>
>> >>> Vincent
>> >>>
>> >>> Le 21/04/2019 à 13:22, Vincent Delecroix a écrit :
>> >>>> Dear all,
>> >>>>
>> >>>> Starting from scratch, I failed to build sagenb. More precisely,
>> >>>> it failed building its documentation with
>> >>>>
>> >>>> Running Sphinx v1.8.5
>> >>>> making output directory...
>> >>>> building [mo]: targets for 0 po files that are out of date
>> >>>> building [html]: targets for 19 source files that are out of date
>> >>>> updating environment: 19 added, 0 changed, 0 removed
>> >>>> reading sources... [ 5%] index
>> >>>> reading sources... [ 10%] misc/introspect
>> >>>> reading sources... [ 15%] misc/misc
>> >>>>
>> >>>> Exception occurred:
>> >>>> File "sage/misc/lazy_import.pyx", line 218, in
>> >>>> sage.misc.lazy_import.LazyImport._get_object
>> >>>> (build/cythonized/sage/misc/lazy_import.c:2495)
>> >>>> raise RuntimeError(f"resolving lazy import {self._name} during
>> >>>> startup")
>> >>>> RuntimeError: resolving lazy import dumps during startup
>> >>>>
>> >>>> See also the more complete log in attachment.
>> >>>>
>> >>>> Vincent
>> >>
>> >> --
>> >> 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-...@googlegroups.com.
>> >> To post to this group, send email to sage-...@googlegroups.com.
>> >> Visit this group at https://groups.google.com/group/sage-devel.
>> >> For more options, visit https://groups.google.com/d/optout.
>> >>
>> >
>
> --
> 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 https://groups.google.com/group/sage-devel.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/85ea0bea-c855-47fa-b82e-f21d2594cd95%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
--
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 https://groups.google.com/group/sage-devel.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAAWYfq2tQBgdhAcCBQJspdqwz04Ga7KUi5a_qPkU%3DxZxkNP%2BkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
