I looked into build/pgks/* (1.5 GB) and it appears that Sage is trying to
be a package manager, in addition to what people probably want it for.
I guess at version 9.2 it's rather late to ask why it isn't good enough to
just list in the README a set of packages that Sage requires to run, and
h
>
>
>> We don't have a single MacPort user among a handful of SageMath
>>> developers. Please feel free to provide patches. (Yes, it means supporting
>>> yet another nonstandard location, more or less, I suppose)
>>>
>>
>> The fun part is that to support Macports, you need to look in
>> /opt/lo
Please see below.
TL;DR.
> patches are most welcome :-)
>
Understood.
> Sage-9.2 has several idiosyncrasies that for me are hard to explain. One -
>> it deliberately refuses to work with Macports-installed packages, even
>> though their main difference from similar ones installed via Brew is
s.CommandError: Failed to build one or
more wheels
[scipy-1.5.2] Removed build tracker:
'/private/var/folders/_l/4q83bg9j5ysb7qd1n9xpnb4hgn/T/pip-req-tracker-ybfte_50'
[scipy-1.5.2]
[scipy-1.5.2] E
A lot of people have a lot of problems with Sage-9.2 on MacOS, installing
pre-compiled or building from the source.
Sage-9.2 has several idiosyncrasies that for me are hard to explain. One -
it deliberately refuses to work with Macports-installed packages, even
though their main difference from
