I have found the instructions at
https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md
useful for me, as someone used to the old trac interface.
On Saturday, April 8, 2023 at 1:23:06 PM UTC-7 G. M.-S. wrote:
>
> Thanks Dima and Drew.
>
> I had the very same
Thank you, this allows sage to complete the build. However, now I have
another problem. When I run sage from its install directory it gives the
error:
AttributeError: module 'sage_conf' has no attribute '_main'
And then strangely, it starts Sage 9.5, the version installed on my system
through
Thanks Dima and Drew.
I had the very same question, but zero ways for doing it, so I did not dare
ask…
Guillermo
On Sat, 8 Apr 2023 at 22:14, Dima Pasechnik wrote:
>
> On Sat, 8 Apr 2023, 20:24 Drew Shotwell, wrote:
>
>> I'm looking into working on an issue in git, and I'm wondering how to
On Sat, 8 Apr 2023, 20:24 Drew Shotwell, wrote:
> I'm looking into working on an issue in git, and I'm wondering how to
> properly go about testing someone else's branch. Let's take for instance
> https://github.com/sagemath/sage/pull/35414.
suppose you have remote foo set to
I'm looking into working on an issue in git, and I'm wondering how to
properly go about testing someone else's branch. Let's take for instance
https://github.com/sagemath/sage/pull/35414. Essentially what I want to do
is get the code changes from the forked branch
Le 07/04/2023 à 23:53, John H Palmieri a écrit :
Some recent versions of Singular don't seem to work with Sage. You could
try "make distclean" (to start over) and "./configure
--with-system-singular=no" to force Sage to build its own Singular. Then
"make".
Yes, I had the same problem on