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
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
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:
> >
>
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
>
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
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,
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,
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
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
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.
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
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
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
13 matches
Mail list logo
