Re: [sage-devel] Where do categories() come from?
On 8/5/19 11:24 PM, Michael Orlitzky wrote: > > I guess FiniteDimensionalAlgebrasWithBasis has both the old Algebras() > and the new MagmaticAlgebras() as supercategories? That would explain > why I'm seeing associativity and rings everywhere. > ...and building up a pile of non-associative categories one-at-a-time doesn't work either, of course =) Hopefully-simple fixes in https://trac.sagemath.org/ticket/28327 and https://trac.sagemath.org/ticket/28328 if anyone has a minute. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/21d8a03e-ef66-9b80-3961-45c3db04dd9f%40orlitzky.com.
Re: [sage-devel] sage build fail
On Wed, Aug 7, 2019 at 9:29 PM Holley Friedlander wrote:
>
> I tried
>
> ls /usr/lib/system/libsystem_darwin.dylib
>
> but I get the message "no such file or directory". Maybe I am looking in the
> wrong place? Thanks.
no, this means that this fix didn't work.
Perhaps you ought to reinstall/upgrade Command Line Tools for Xcode
or/and Xcode itself.
>
>
> On Wednesday, August 7, 2019 at 1:21:41 PM UTC-5, Dima Pasechnik wrote:
>>
>> On Wed, Aug 7, 2019 at 9:15 PM Holley Friedlander wrote:
>> >
>> > Thank you. So I ran the line you suggested below. Is there a way to check
>> > it or should I retype "make" now? This is the warning from my original
>> > error message. Should I change this environment variable? How do I do
>> > this? Is it something I type after make? I apologize, I am new to this.
>>
>> you can check if the fix did what it shoud do, i.e. installed
>> /usr/lib/system/libsystem_darwin.dylib
>>
>> In the terminal, type
>>
>> ls /usr/lib/system/libsystem_darwin.dylib
>>
>> and check that it outputs the file name
>> Assuming it worked, to speed things up,
>> you need to rebuild python2 package, by e.g.
>>
>> ./sage -f python2
>>
>> and then run
>>
>> make
>>
>>
>>
>> >
>> > The build directory may contain configuration files and other potentially
>> >
>> > helpful information. WARNING: if you now run 'make' again, the build
>> >
>> > directory will, by default, be deleted. Set the environment variable
>> >
>> > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>> >
>> >
>> > On Wednesday, August 7, 2019 at 12:14:18 PM UTC-5, Dima Pasechnik wrote:
>> >>
>> >> indeed, you will see in the log
>> >>
>> >> ld: file not found: /usr/lib/system/libsystem_darwin.dylib for
>> >> architecture x86_64
>> >>
>> >> which indicates that your Xcode installation is somewhat broken.
>> >> Internet says you'd need to run
>> >>
>> >> sudo xcode-select -s /Library/Developer/CommandLineTools
>> >>
>> >> to fix this. (YMMV, naturally...)
>> >>
>> >>
>> >> On Wed, Aug 7, 2019 at 6:15 PM Holley Friedlander
>> >> wrote:
>> >> >
>> >> > Okay here it is. I had to compress it as it was too large to attach
>> >> > otherwise.
>> >> >
>> >> > On Wednesday, August 7, 2019 at 10:06:45 AM UTC-5, Dima Pasechnik wrote:
>> >> >>
>> >> >> So the sqlite module of Python2 was not built correctly, it seems.
>> >> >> Please post
>> >> >> logs/pkgs/python2-2.7.15.p1.log
>> >> >>
>> >> >> On Wed, Aug 7, 2019 at 5:27 PM Holley Friedlander
>> >> >> wrote:
>> >> >> >
>> >> >> > Thank you. I tried the ./sage and this is the crash report
>> >> >> > (attached).
>> >> >> >
>> >> >> > On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5, E. Madison Bray
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Hello,
>> >> >> >>
>> >> >> >> This happens in general because the sagenb package uses sage itself
>> >> >> >> as
>> >> >> >> a dependency, so once the build process gets to installing sagenb
>> >> >> >> (specifically building its documentation) if something is wrong with
>> >> >> >> the *sage* build your build will fail here.
>> >> >> >>
>> >> >> >> There have been many cases of this. Just to pick one at random:
>> >> >> >> https://trac.sagemath.org/ticket/26686
>> >> >> >>
>> >> >> >> The question is what is wrong with your sage build. Try running
>> >> >> >>
>> >> >> >> $ ./sage
>> >> >> >>
>> >> >> >> directly. Because by the time the build process is installing
>> >> >> >> sagenb,
>> >> >> >> the core sage library should already be built and working. If not,
>> >> >> >> it
>> >> >> >> will crash, and you'll get a crash log (and hopefully a more useful
>> >> >> >> one, at that).
>> >> >> >>
>> >> >> >> On Wed, Aug 7, 2019 at 3:52 PM Holley Friedlander
>> >> >> >> wrote:
>> >> >> >> >
>> >> >> >> > I had an error building sage. The problem was with the package
>> >> >> >> > sagenb-1.1.2. I am attaching my log file. Here is what I believe
>> >> >> >> > to be the relevant portion. I am on OS v 10.12.6. I found another
>> >> >> >> > thread that suggested this may have something to do with Python
>> >> >> >> > 3, but I am not sure if it is the same issue and I did not
>> >> >> >> > understand the fix. I installed Command Line Tools as
>> >> >> >> > prerequisite to starting the build. Suggestions on how to resolve?
>> >> >> >> >
>> >> >> >> > 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:2502)
>> >> >> >> > raise RuntimeError(f"resolving lazy import {self._name}
>> >> >> >> > during startup")
>> >> >> >> > RuntimeError: resolving lazy import dumps during startup
>> >> >> >> > The full traceback has been saved in
>> >> >> >> > /var/folders/r7/bx5nmhtx23bgx6lhgxlbfj3wgn/T/sphinx-err-3aMcJb.log,
>> >> >> >> > if you want to report the issue to the developers.
>> >> >> >> > Please also report this if it was a user error, so that a better
>> >> >> >> > error message can be provid
Re: [sage-devel] sage build fail
I tried
ls /usr/lib/system/libsystem_darwin.dylib
but I get the message "no such file or directory". Maybe I am looking in
the wrong place? Thanks.
On Wednesday, August 7, 2019 at 1:21:41 PM UTC-5, Dima Pasechnik wrote:
>
> On Wed, Aug 7, 2019 at 9:15 PM Holley Friedlander > wrote:
> >
> > Thank you. So I ran the line you suggested below. Is there a way to
> check it or should I retype "make" now? This is the warning from my
> original error message. Should I change this environment variable? How do I
> do this? Is it something I type after make? I apologize, I am new to this.
>
> you can check if the fix did what it shoud do, i.e. installed
> /usr/lib/system/libsystem_darwin.dylib
>
> In the terminal, type
>
> ls /usr/lib/system/libsystem_darwin.dylib
>
> and check that it outputs the file name
> Assuming it worked, to speed things up,
> you need to rebuild python2 package, by e.g.
>
> ./sage -f python2
>
> and then run
>
> make
>
>
>
> >
> > The build directory may contain configuration files and other
> potentially
> >
> > helpful information. WARNING: if you now run 'make' again, the build
> >
> > directory will, by default, be deleted. Set the environment variable
> >
> > SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
> >
> >
> > On Wednesday, August 7, 2019 at 12:14:18 PM UTC-5, Dima Pasechnik wrote:
> >>
> >> indeed, you will see in the log
> >>
> >> ld: file not found: /usr/lib/system/libsystem_darwin.dylib for
> >> architecture x86_64
> >>
> >> which indicates that your Xcode installation is somewhat broken.
> >> Internet says you'd need to run
> >>
> >> sudo xcode-select -s /Library/Developer/CommandLineTools
> >>
> >> to fix this. (YMMV, naturally...)
> >>
> >>
> >> On Wed, Aug 7, 2019 at 6:15 PM Holley Friedlander
> wrote:
> >> >
> >> > Okay here it is. I had to compress it as it was too large to attach
> otherwise.
> >> >
> >> > On Wednesday, August 7, 2019 at 10:06:45 AM UTC-5, Dima Pasechnik
> wrote:
> >> >>
> >> >> So the sqlite module of Python2 was not built correctly, it seems.
> Please post
> >> >> logs/pkgs/python2-2.7.15.p1.log
> >> >>
> >> >> On Wed, Aug 7, 2019 at 5:27 PM Holley Friedlander
> wrote:
> >> >> >
> >> >> > Thank you. I tried the ./sage and this is the crash report
> (attached).
> >> >> >
> >> >> > On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5, E. Madison Bray
> wrote:
> >> >> >>
> >> >> >> Hello,
> >> >> >>
> >> >> >> This happens in general because the sagenb package uses sage
> itself as
> >> >> >> a dependency, so once the build process gets to installing sagenb
> >> >> >> (specifically building its documentation) if something is wrong
> with
> >> >> >> the *sage* build your build will fail here.
> >> >> >>
> >> >> >> There have been many cases of this. Just to pick one at random:
> >> >> >> https://trac.sagemath.org/ticket/26686
> >> >> >>
> >> >> >> The question is what is wrong with your sage build. Try running
> >> >> >>
> >> >> >> $ ./sage
> >> >> >>
> >> >> >> directly. Because by the time the build process is installing
> sagenb,
> >> >> >> the core sage library should already be built and working. If
> not, it
> >> >> >> will crash, and you'll get a crash log (and hopefully a more
> useful
> >> >> >> one, at that).
> >> >> >>
> >> >> >> On Wed, Aug 7, 2019 at 3:52 PM Holley Friedlander <
> holl...@gmail.com> wrote:
> >> >> >> >
> >> >> >> > I had an error building sage. The problem was with the package
> sagenb-1.1.2. I am attaching my log file. Here is what I believe to be the
> relevant portion. I am on OS v 10.12.6. I found another thread that
> suggested this may have something to do with Python 3, but I am not sure if
> it is the same issue and I did not understand the fix. I installed Command
> Line Tools as prerequisite to starting the build. Suggestions on how to
> resolve?
> >> >> >> >
> >> >> >> > 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:2502)
> >> >> >> > raise RuntimeError(f"resolving lazy import {self._name}
> during startup")
> >> >> >> > RuntimeError: resolving lazy import dumps during startup
> >> >> >> > The full traceback has been saved in
> /var/folders/r7/bx5nmhtx23bgx6lhgxlbfj3wgn/T/sphinx-err-3aMcJb.log, if
> you want to report the issue to the developers.
> >> >> >> > Please also report this if it was a user error, so that a
> better error message can be provided next time.
> >> >> >> > A bug report can be filed in the tracker at <
> https://github.com/sphinx-doc/sphinx/issues>. Thanks!
> >> >> >> > make[4]: *** [html] Error 2
> >> >> >> >
>
>
>
> >> >> >> > Error building the documentation
> >> >> >> >
>
>
Re: [sage-devel] sage build fail
On Wed, Aug 7, 2019 at 9:15 PM Holley Friedlander wrote:
>
> Thank you. So I ran the line you suggested below. Is there a way to check it
> or should I retype "make" now? This is the warning from my original error
> message. Should I change this environment variable? How do I do this? Is it
> something I type after make? I apologize, I am new to this.
you can check if the fix did what it shoud do, i.e. installed
/usr/lib/system/libsystem_darwin.dylib
In the terminal, type
ls /usr/lib/system/libsystem_darwin.dylib
and check that it outputs the file name
Assuming it worked, to speed things up,
you need to rebuild python2 package, by e.g.
./sage -f python2
and then run
make
>
> The build directory may contain configuration files and other potentially
>
> helpful information. WARNING: if you now run 'make' again, the build
>
> directory will, by default, be deleted. Set the environment variable
>
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
>
>
> On Wednesday, August 7, 2019 at 12:14:18 PM UTC-5, Dima Pasechnik wrote:
>>
>> indeed, you will see in the log
>>
>> ld: file not found: /usr/lib/system/libsystem_darwin.dylib for
>> architecture x86_64
>>
>> which indicates that your Xcode installation is somewhat broken.
>> Internet says you'd need to run
>>
>> sudo xcode-select -s /Library/Developer/CommandLineTools
>>
>> to fix this. (YMMV, naturally...)
>>
>>
>> On Wed, Aug 7, 2019 at 6:15 PM Holley Friedlander wrote:
>> >
>> > Okay here it is. I had to compress it as it was too large to attach
>> > otherwise.
>> >
>> > On Wednesday, August 7, 2019 at 10:06:45 AM UTC-5, Dima Pasechnik wrote:
>> >>
>> >> So the sqlite module of Python2 was not built correctly, it seems. Please
>> >> post
>> >> logs/pkgs/python2-2.7.15.p1.log
>> >>
>> >> On Wed, Aug 7, 2019 at 5:27 PM Holley Friedlander
>> >> wrote:
>> >> >
>> >> > Thank you. I tried the ./sage and this is the crash report (attached).
>> >> >
>> >> > On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5, E. Madison Bray wrote:
>> >> >>
>> >> >> Hello,
>> >> >>
>> >> >> This happens in general because the sagenb package uses sage itself as
>> >> >> a dependency, so once the build process gets to installing sagenb
>> >> >> (specifically building its documentation) if something is wrong with
>> >> >> the *sage* build your build will fail here.
>> >> >>
>> >> >> There have been many cases of this. Just to pick one at random:
>> >> >> https://trac.sagemath.org/ticket/26686
>> >> >>
>> >> >> The question is what is wrong with your sage build. Try running
>> >> >>
>> >> >> $ ./sage
>> >> >>
>> >> >> directly. Because by the time the build process is installing sagenb,
>> >> >> the core sage library should already be built and working. If not, it
>> >> >> will crash, and you'll get a crash log (and hopefully a more useful
>> >> >> one, at that).
>> >> >>
>> >> >> On Wed, Aug 7, 2019 at 3:52 PM Holley Friedlander
>> >> >> wrote:
>> >> >> >
>> >> >> > I had an error building sage. The problem was with the package
>> >> >> > sagenb-1.1.2. I am attaching my log file. Here is what I believe to
>> >> >> > be the relevant portion. I am on OS v 10.12.6. I found another
>> >> >> > thread that suggested this may have something to do with Python 3,
>> >> >> > but I am not sure if it is the same issue and I did not understand
>> >> >> > the fix. I installed Command Line Tools as prerequisite to starting
>> >> >> > the build. Suggestions on how to resolve?
>> >> >> >
>> >> >> > 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:2502)
>> >> >> > raise RuntimeError(f"resolving lazy import {self._name} during
>> >> >> > startup")
>> >> >> > RuntimeError: resolving lazy import dumps during startup
>> >> >> > The full traceback has been saved in
>> >> >> > /var/folders/r7/bx5nmhtx23bgx6lhgxlbfj3wgn/T/sphinx-err-3aMcJb.log,
>> >> >> > if you want to report the issue to the developers.
>> >> >> > Please also report this if it was a user error, so that a better
>> >> >> > error message can be provided next time.
>> >> >> > A bug report can be filed in the tracker at
>> >> >> > . Thanks!
>> >> >> > make[4]: *** [html] Error 2
>> >> >> >
>> >> >> > Error building the documentation
>> >> >> >
>> >> >> >
>> >> >> > real 0m7.502s
>> >> >> > user 0m5.810s
>> >> >> > sys 0m2.151s
>> >> >> >
>> >> >> > Error installing package sagenb-1.1.2
>> >> >> >
>> >> >> >
>> >> >> > --
>> >> >> > You received this message because you are subscribed to the Google
>> >> >> > Groups "sa
Re: [sage-devel] sage build fail
Thank you. So I ran the line you suggested below. Is there a way to check
it or should I retype "make" now? This is the warning from my original
error message. Should I change this environment variable? How do I do this?
Is it something I type after make? I apologize, I am new to this.
The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.
On Wednesday, August 7, 2019 at 12:14:18 PM UTC-5, Dima Pasechnik wrote:
>
> indeed, you will see in the log
>
> ld: file not found: /usr/lib/system/libsystem_darwin.dylib for
> architecture x86_64
>
> which indicates that your Xcode installation is somewhat broken.
> Internet says you'd need to run
>
> sudo xcode-select -s /Library/Developer/CommandLineTools
>
> to fix this. (YMMV, naturally...)
>
>
> On Wed, Aug 7, 2019 at 6:15 PM Holley Friedlander > wrote:
> >
> > Okay here it is. I had to compress it as it was too large to attach
> otherwise.
> >
> > On Wednesday, August 7, 2019 at 10:06:45 AM UTC-5, Dima Pasechnik wrote:
> >>
> >> So the sqlite module of Python2 was not built correctly, it seems.
> Please post
> >> logs/pkgs/python2-2.7.15.p1.log
> >>
> >> On Wed, Aug 7, 2019 at 5:27 PM Holley Friedlander
> wrote:
> >> >
> >> > Thank you. I tried the ./sage and this is the crash report
> (attached).
> >> >
> >> > On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5, E. Madison Bray
> wrote:
> >> >>
> >> >> Hello,
> >> >>
> >> >> This happens in general because the sagenb package uses sage itself
> as
> >> >> a dependency, so once the build process gets to installing sagenb
> >> >> (specifically building its documentation) if something is wrong with
> >> >> the *sage* build your build will fail here.
> >> >>
> >> >> There have been many cases of this. Just to pick one at random:
> >> >> https://trac.sagemath.org/ticket/26686
> >> >>
> >> >> The question is what is wrong with your sage build. Try running
> >> >>
> >> >> $ ./sage
> >> >>
> >> >> directly. Because by the time the build process is installing
> sagenb,
> >> >> the core sage library should already be built and working. If not,
> it
> >> >> will crash, and you'll get a crash log (and hopefully a more useful
> >> >> one, at that).
> >> >>
> >> >> On Wed, Aug 7, 2019 at 3:52 PM Holley Friedlander
> wrote:
> >> >> >
> >> >> > I had an error building sage. The problem was with the package
> sagenb-1.1.2. I am attaching my log file. Here is what I believe to be the
> relevant portion. I am on OS v 10.12.6. I found another thread that
> suggested this may have something to do with Python 3, but I am not sure if
> it is the same issue and I did not understand the fix. I installed Command
> Line Tools as prerequisite to starting the build. Suggestions on how to
> resolve?
> >> >> >
> >> >> > 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:2502)
> >> >> > raise RuntimeError(f"resolving lazy import {self._name} during
> startup")
> >> >> > RuntimeError: resolving lazy import dumps during startup
> >> >> > The full traceback has been saved in
> /var/folders/r7/bx5nmhtx23bgx6lhgxlbfj3wgn/T/sphinx-err-3aMcJb.log, if
> you want to report the issue to the developers.
> >> >> > Please also report this if it was a user error, so that a better
> error message can be provided next time.
> >> >> > A bug report can be filed in the tracker at <
> https://github.com/sphinx-doc/sphinx/issues>. Thanks!
> >> >> > make[4]: *** [html] Error 2
> >> >> >
>
>
>
> >> >> > Error building the documentation
> >> >> >
>
>
>
> >> >> >
> >> >> > real 0m7.502s
> >> >> > user 0m5.810s
> >> >> > sys 0m2.151s
> >> >> >
>
> >> >> > Error installing package sagenb-1.1.2
> >> >> >
>
> >> >> >
> >> >> > --
> >> >> > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/db4dd9c1-b83f-49d9-b80e-cd9d8b60f4cb%40googlegroups.com.
>
>
> >> >
> >> > --
> >> > 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-...@googl
Re: [sage-devel] sage build fail
indeed, you will see in the log
ld: file not found: /usr/lib/system/libsystem_darwin.dylib for
architecture x86_64
which indicates that your Xcode installation is somewhat broken.
Internet says you'd need to run
sudo xcode-select -s /Library/Developer/CommandLineTools
to fix this. (YMMV, naturally...)
On Wed, Aug 7, 2019 at 6:15 PM Holley Friedlander wrote:
>
> Okay here it is. I had to compress it as it was too large to attach otherwise.
>
> On Wednesday, August 7, 2019 at 10:06:45 AM UTC-5, Dima Pasechnik wrote:
>>
>> So the sqlite module of Python2 was not built correctly, it seems. Please
>> post
>> logs/pkgs/python2-2.7.15.p1.log
>>
>> On Wed, Aug 7, 2019 at 5:27 PM Holley Friedlander wrote:
>> >
>> > Thank you. I tried the ./sage and this is the crash report (attached).
>> >
>> > On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5, E. Madison Bray wrote:
>> >>
>> >> Hello,
>> >>
>> >> This happens in general because the sagenb package uses sage itself as
>> >> a dependency, so once the build process gets to installing sagenb
>> >> (specifically building its documentation) if something is wrong with
>> >> the *sage* build your build will fail here.
>> >>
>> >> There have been many cases of this. Just to pick one at random:
>> >> https://trac.sagemath.org/ticket/26686
>> >>
>> >> The question is what is wrong with your sage build. Try running
>> >>
>> >> $ ./sage
>> >>
>> >> directly. Because by the time the build process is installing sagenb,
>> >> the core sage library should already be built and working. If not, it
>> >> will crash, and you'll get a crash log (and hopefully a more useful
>> >> one, at that).
>> >>
>> >> On Wed, Aug 7, 2019 at 3:52 PM Holley Friedlander
>> >> wrote:
>> >> >
>> >> > I had an error building sage. The problem was with the package
>> >> > sagenb-1.1.2. I am attaching my log file. Here is what I believe to be
>> >> > the relevant portion. I am on OS v 10.12.6. I found another thread that
>> >> > suggested this may have something to do with Python 3, but I am not
>> >> > sure if it is the same issue and I did not understand the fix. I
>> >> > installed Command Line Tools as prerequisite to starting the build.
>> >> > Suggestions on how to resolve?
>> >> >
>> >> > 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:2502)
>> >> > raise RuntimeError(f"resolving lazy import {self._name} during
>> >> > startup")
>> >> > RuntimeError: resolving lazy import dumps during startup
>> >> > The full traceback has been saved in
>> >> > /var/folders/r7/bx5nmhtx23bgx6lhgxlbfj3wgn/T/sphinx-err-3aMcJb.log,
>> >> > if you want to report the issue to the developers.
>> >> > Please also report this if it was a user error, so that a better error
>> >> > message can be provided next time.
>> >> > A bug report can be filed in the tracker at
>> >> > . Thanks!
>> >> > make[4]: *** [html] Error 2
>> >> >
>> >> > Error building the documentation
>> >> >
>> >> >
>> >> > real 0m7.502s
>> >> > user 0m5.810s
>> >> > sys 0m2.151s
>> >> >
>> >> > Error installing package sagenb-1.1.2
>> >> >
>> >> >
>> >> > --
>> >> > 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 view this discussion on the web visit
>> >> > https://groups.google.com/d/msgid/sage-devel/db4dd9c1-b83f-49d9-b80e-cd9d8b60f4cb%40googlegroups.com.
>> >
>> > --
>> > 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 view this discussion on the web visit
>> > https://groups.google.com/d/msgid/sage-devel/debf8df5-5e74-4cf7-8603-c657d4831c66%40googlegroups.com.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/66441a0a-8176-480d-8b41-69914219f116%40googlegroups.com.
--
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 view this discus
Re: [sage-devel] sage build fail
So the sqlite module of Python2 was not built correctly, it seems. Please post
logs/pkgs/python2-2.7.15.p1.log
On Wed, Aug 7, 2019 at 5:27 PM Holley Friedlander wrote:
>
> Thank you. I tried the ./sage and this is the crash report (attached).
>
> On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5, E. Madison Bray wrote:
>>
>> Hello,
>>
>> This happens in general because the sagenb package uses sage itself as
>> a dependency, so once the build process gets to installing sagenb
>> (specifically building its documentation) if something is wrong with
>> the *sage* build your build will fail here.
>>
>> There have been many cases of this. Just to pick one at random:
>> https://trac.sagemath.org/ticket/26686
>>
>> The question is what is wrong with your sage build. Try running
>>
>> $ ./sage
>>
>> directly. Because by the time the build process is installing sagenb,
>> the core sage library should already be built and working. If not, it
>> will crash, and you'll get a crash log (and hopefully a more useful
>> one, at that).
>>
>> On Wed, Aug 7, 2019 at 3:52 PM Holley Friedlander wrote:
>> >
>> > I had an error building sage. The problem was with the package
>> > sagenb-1.1.2. I am attaching my log file. Here is what I believe to be the
>> > relevant portion. I am on OS v 10.12.6. I found another thread that
>> > suggested this may have something to do with Python 3, but I am not sure
>> > if it is the same issue and I did not understand the fix. I installed
>> > Command Line Tools as prerequisite to starting the build. Suggestions on
>> > how to resolve?
>> >
>> > 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:2502)
>> > raise RuntimeError(f"resolving lazy import {self._name} during
>> > startup")
>> > RuntimeError: resolving lazy import dumps during startup
>> > The full traceback has been saved in
>> > /var/folders/r7/bx5nmhtx23bgx6lhgxlbfj3wgn/T/sphinx-err-3aMcJb.log, if
>> > you want to report the issue to the developers.
>> > Please also report this if it was a user error, so that a better error
>> > message can be provided next time.
>> > A bug report can be filed in the tracker at
>> > . Thanks!
>> > make[4]: *** [html] Error 2
>> >
>> > Error building the documentation
>> >
>> >
>> > real 0m7.502s
>> > user 0m5.810s
>> > sys 0m2.151s
>> >
>> > Error installing package sagenb-1.1.2
>> >
>> >
>> > --
>> > 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 view this discussion on the web visit
>> > https://groups.google.com/d/msgid/sage-devel/db4dd9c1-b83f-49d9-b80e-cd9d8b60f4cb%40googlegroups.com.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/debf8df5-5e74-4cf7-8603-c657d4831c66%40googlegroups.com.
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAAWYfq2mCbNyKv4zJWiza4%2BKbDdBcN466n_c4b-fiAs%3DvUFQ3A%40mail.gmail.com.
Re: [sage-devel] sage build fail
Thank you. I tried the ./sage and this is the crash report (attached).
On Wednesday, August 7, 2019 at 9:13:38 AM UTC-5, E. Madison Bray wrote:
>
> Hello,
>
> This happens in general because the sagenb package uses sage itself as
> a dependency, so once the build process gets to installing sagenb
> (specifically building its documentation) if something is wrong with
> the *sage* build your build will fail here.
>
> There have been many cases of this. Just to pick one at random:
> https://trac.sagemath.org/ticket/26686
>
> The question is what is wrong with your sage build. Try running
>
> $ ./sage
>
> directly. Because by the time the build process is installing sagenb,
> the core sage library should already be built and working. If not, it
> will crash, and you'll get a crash log (and hopefully a more useful
> one, at that).
>
> On Wed, Aug 7, 2019 at 3:52 PM Holley Friedlander > wrote:
> >
> > I had an error building sage. The problem was with the package
> sagenb-1.1.2. I am attaching my log file. Here is what I believe to be the
> relevant portion. I am on OS v 10.12.6. I found another thread that
> suggested this may have something to do with Python 3, but I am not sure if
> it is the same issue and I did not understand the fix. I installed Command
> Line Tools as prerequisite to starting the build. Suggestions on how to
> resolve?
> >
> > 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:2502)
> > raise RuntimeError(f"resolving lazy import {self._name} during
> startup")
> > RuntimeError: resolving lazy import dumps during startup
> > The full traceback has been saved in
> /var/folders/r7/bx5nmhtx23bgx6lhgxlbfj3wgn/T/sphinx-err-3aMcJb.log, if
> you want to report the issue to the developers.
> > Please also report this if it was a user error, so that a better error
> message can be provided next time.
> > A bug report can be filed in the tracker at <
> https://github.com/sphinx-doc/sphinx/issues>. Thanks!
> > make[4]: *** [html] Error 2
> >
>
>
>
> > Error building the documentation
> >
>
>
>
> >
> > real 0m7.502s
> > user 0m5.810s
> > sys 0m2.151s
> >
> > Error installing package sagenb-1.1.2
> >
> >
> > --
> > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/db4dd9c1-b83f-49d9-b80e-cd9d8b60f4cb%40googlegroups.com.
>
>
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/debf8df5-5e74-4cf7-8603-c657d4831c66%40googlegroups.com.
***
IPython post-mortem report
{'commit_hash': u'033ab93c7',
'commit_source': 'installation',
'default_encoding': 'UTF-8',
'ipython_path':
'/Users/friedlah/Documents/sagedev/local/lib/python2.7/site-packages/IPython',
'ipython_version': '5.8.0',
'os_name': 'posix',
'platform': 'Darwin-16.7.0-x86_64-i386-64bit',
'sys_executable': '/Users/friedlah/Documents/sagedev/local/bin/python2',
'sys_platform': 'darwin',
'sys_version': '2.7.15 (default, Aug 6 2019, 07:42:03) \n[GCC 4.2.1
Compatible Apple LLVM 9.0.0 (clang-900.0.39.2)]'}
***
***
Crash traceback:
---
---
ImportErrorPython 2.7.15: /Users/friedlah/Documents/sagedev/local/bin/python2
Wed Aug 7 09:19:53 2019
A problem occurred executing Python code. Here is the sequence of function
calls leading up to the error, with the most recent (innermost) call last.
/Users/friedlah/Documents/sagedev/src/bin/sage-ipython in ()
1 #!/usr/bin/env sage-python23
2 # -*- coding: utf-8 -*-
3 """
4 Sage IPython startup script.
5 """
6
7 # Display startup banner. Do this before anything else to give the user
8 # early feedback that Sage is starting.
9 from sage.misc.banner impo
Re: [sage-devel] Making Integer and Rational compatible with Python Fraction
On Wed, Aug 7, 2019 at 3:50 PM Jeroen Demeyer wrote: > > On 2019-08-07 15:42, E. Madison Bray wrote: > > What if, at some point, we just make a Sage release that breaks > > backwards compatibility? > > We could, but I don't think that PEP 3141 is worth breaking backwards > compatibility for. I'm inclined to agree, unfortunately. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34a23AU%3DOca9SCgXwyuqALZrX358p_8v5XaFn%2BPb2d%3DPGg%40mail.gmail.com.
Re: [sage-devel] sage build fail
Hello,
This happens in general because the sagenb package uses sage itself as
a dependency, so once the build process gets to installing sagenb
(specifically building its documentation) if something is wrong with
the *sage* build your build will fail here.
There have been many cases of this. Just to pick one at random:
https://trac.sagemath.org/ticket/26686
The question is what is wrong with your sage build. Try running
$ ./sage
directly. Because by the time the build process is installing sagenb,
the core sage library should already be built and working. If not, it
will crash, and you'll get a crash log (and hopefully a more useful
one, at that).
On Wed, Aug 7, 2019 at 3:52 PM Holley Friedlander wrote:
>
> I had an error building sage. The problem was with the package sagenb-1.1.2.
> I am attaching my log file. Here is what I believe to be the relevant
> portion. I am on OS v 10.12.6. I found another thread that suggested this may
> have something to do with Python 3, but I am not sure if it is the same issue
> and I did not understand the fix. I installed Command Line Tools as
> prerequisite to starting the build. Suggestions on how to resolve?
>
> 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:2502)
> raise RuntimeError(f"resolving lazy import {self._name} during startup")
> RuntimeError: resolving lazy import dumps during startup
> The full traceback has been saved in
> /var/folders/r7/bx5nmhtx23bgx6lhgxlbfj3wgn/T/sphinx-err-3aMcJb.log, if
> you want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> . Thanks!
> make[4]: *** [html] Error 2
>
> Error building the documentation
>
>
> real 0m7.502s
> user 0m5.810s
> sys 0m2.151s
>
> Error installing package sagenb-1.1.2
>
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/db4dd9c1-b83f-49d9-b80e-cd9d8b60f4cb%40googlegroups.com.
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/CAOTD34Zf45F5g1a9%3Dqx72gQpXANBServHiC6RB2hszpquh53Ww%40mail.gmail.com.
Re: [sage-devel] Making Integer and Rational compatible with Python Fraction
On 2019-08-07 15:42, E. Madison Bray wrote: What if, at some point, we just make a Sage release that breaks backwards compatibility? We could, but I don't think that PEP 3141 is worth breaking backwards compatibility for. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/5D4AD707.8050901%40UGent.be.
Re: [sage-devel] Making Integer and Rational compatible with Python Fraction
On Sun, Aug 4, 2019 at 11:04 PM Jeroen Demeyer wrote: > > On 2019-07-27 18:49, 'Mark Bell' via sage-devel wrote: > > During Sage Days 100, I experienced an issue with Sage's Integers and > > Rational not being compatible with Python's built in Fraction class. > > This made me unable to run my Python code within Sage > > It would be good to explain better exactly what kind of code you were > running and why this is an issue for you. > > I mentioned this issue to the Python devs and Guido van Rossum basically > rejected the problem. He literally said "what real-world problem does > that solve?" when talking about letting Python fractions interoperate > with Sage fractions, see > https://discuss.python.org/t/pep-3141-ratio-instead-of-numerator-denominator/2037/27?u=jdemeyer > > If this would be a simple bugfix, I would dismiss Guido's comment as > irrelevant. But in this case, there is no easy fix. Every proposed fix > is somewhat backwards incompatible and can potentially break stuff. So > we should only apply a fix if it will actually solve a real problem that > people are encountering. What if, at some point, we just make a Sage release that breaks backwards compatibility? It doesn't have to be as huge a breakage as Python 2 -> Python 3. But sometimes it's just necessary to bite the bullet and break things. That's what version numbering is for. It would help, of course, if every current Sage release weren't an arbitrary mix of enhancements and bug fixes. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAOTD34Y4JHjMmc7TmFg8XXhGwrrSubvOjuxcJPHEQxiMvQXb_w%40mail.gmail.com.
Re: [sage-devel] Making Integer and Rational compatible with Python Fraction
On 2019-08-06 17:30, TB wrote: sage: plot(lambda x: x.imag + 2) # Works sage: plot(lambda x: x.imag() + 2, (x, -3, 3)) # Empty plot That's "only" an annoyance: you need to use x.imag or x.imag() depending on what x is. That's not a problem of interoperability. And if you really want generic code, you can always write complex(x).imag (at some performance cost). So it's less a problem than Fraction. To add another data point about triggering unexpected computations, numpy.array does have .real and .imag properties. As far as I can see, it doesn't actually use .real or .imag on the objects that it wraps, so again there is no problem here. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/5D4A9F40.9080408%40UGent.be.
