Have you tried reinstalling the command-line tools?
On Tuesday, June 21, 2022 at 6:44:54 AM UTC-7 gcha...@vols.utk.edu wrote:
> Hello,
> I recently updated my computer and XCode, which seems to have broken my
> ability to compile sage. I have tried fully uninstalling and reinstalling,
> making
On Tue, 21 Jun 2022, 15:06 TB, wrote:
> On 21/06/2022 16:35, Dima Pasechnik wrote:
> > On Tue, Jun 21, 2022 at 10:19 AM Dima Pasechnik
> wrote:
> >>
> >> On Tue, Jun 21, 2022 at 4:06 AM Nils Bruin wrote:
> >>>
> >>> Perhaps this message (see the thread it's in for context) applies to
> your
On 21/06/2022 16:35, Dima Pasechnik wrote:
On Tue, Jun 21, 2022 at 10:19 AM Dima Pasechnik wrote:
On Tue, Jun 21, 2022 at 4:06 AM Nils Bruin wrote:
Perhaps this message (see the thread it's in for context) applies to your
situation?
Hello,
I recently updated my computer and XCode, which seems to have broken my
ability to compile sage. I have tried fully uninstalling and reinstalling,
making sure to follow all the MacOS pre-installation recommendations.
However, I keep getting the "C compiler cannot create executables"
On Tue, Jun 21, 2022 at 10:19 AM Dima Pasechnik wrote:
>
> On Tue, Jun 21, 2022 at 4:06 AM Nils Bruin wrote:
> >
> > Perhaps this message (see the thread it's in for context) applies to your
> > situation?
> >
> > https://groups.google.com/g/sage-devel/c/ntuqDmruI8w/m/vJOv6mgqCgAJ
>
> this is
Hi Travis,
Ah got it. Thanks so much!
Best Regards,
Trevor Karn
On Mon, Jun 20, 2022 at 8:11 PM 'Travis Scrimshaw' via sage-devel <
sage-devel@googlegroups.com> wrote:
> Hi Trevor,
>Right...I remember coming across this problem before. Since I know this
> class is for internal use
On Tue, 21 Jun 2022, 10:45 David Joyner, wrote:
> On Tue, Jun 21, 2022 at 5:19 AM Dima Pasechnik wrote:
> >
> > On Tue, Jun 21, 2022 at 4:06 AM Nils Bruin wrote:
> > >
> > > Perhaps this message (see the thread it's in for context) applies to
> your situation?
> > >
> > >
On Tue, Jun 21, 2022 at 5:19 AM Dima Pasechnik wrote:
>
> On Tue, Jun 21, 2022 at 4:06 AM Nils Bruin wrote:
> >
> > Perhaps this message (see the thread it's in for context) applies to your
> > situation?
> >
> > https://groups.google.com/g/sage-devel/c/ntuqDmruI8w/m/vJOv6mgqCgAJ
>
> this is
On Tue, Jun 21, 2022 at 10:19 AM Dima Pasechnik wrote:
>
> On Tue, Jun 21, 2022 at 4:06 AM Nils Bruin wrote:
> >
> > Perhaps this message (see the thread it's in for context) applies to your
> > situation?
> >
> > https://groups.google.com/g/sage-devel/c/ntuqDmruI8w/m/vJOv6mgqCgAJ
>
> this is
On Tue, Jun 21, 2022 at 4:06 AM Nils Bruin wrote:
>
> Perhaps this message (see the thread it's in for context) applies to your
> situation?
>
> https://groups.google.com/g/sage-devel/c/ntuqDmruI8w/m/vJOv6mgqCgAJ
this is outdated. However, it seems that the very old doc suggestion in
Hi,
I am checking whether I should open a ticket. Any comment is welcome.
Cheers,
Denis
save_session() in Sage 9.5 has problems with ETuple variables:
sage: from sage.rings.polynomial.polydict import ETuple
sage: key = ETuple((1,2,3,4))
sage: save_session('data/sessions/example')
On Tue, 21 Jun 2022, 01:59 John H Palmieri, wrote:
> According to
> https://ask.sagemath.org/question/61829/how-to-deal-with-gaperror-error-reached-the-pre-set-memory-limit/,
> try "sage.interfaces.gap.gap_cmd = 'gap -r -o 4G '".
please see
commit 1ea7b697e812302dfca03a1c7fe41c9a8dc3c98e
@Vincent
> I think it is desirable to use the same argument conventions as the
> method VectorField.plot(). In particular use `scale` and not `scaled`.
> I don't know whether VectorField.plot() supports a default rescaling
> as you proposed.
>
Ok let us change into `scale`. Also I have a new
As far as I can tell the actionable part of that thread is Dima's
suggestion to use the function set_gap_memory_pool_size() from
interfaces/gap.py but as I pointed out above, that function has disappeared
from sage-9.5 onwards.
Best,
Alex
On Tuesday, June 21, 2022 at 1:06:15 PM UTC+10 Nils
14 matches
Mail list logo
