On Fri, 15 Apr 2022, 04:04 François Bissey, wrote:
> https://downforeveryoneorjustme.com/trac.sagemat.org
> says it’s not just you or me.
>
sagemat is down, but sagemath is ok.
> > On 15/04/2022, at 13:50, Yueqi Li wrote:
> >
> > Hi,
> >
> > I'm unable to access trac.sagemath.org. I'm
Thank you so much! I can access now!
Best,
Nicole Yueqi
On Thursday, April 14, 2022 at 10:04:59 PM UTC-4 François Bissey wrote:
> https://downforeveryoneorjustme.com/trac.sagemat.org
> says it’s not just you or me.
>
> > On 15/04/2022, at 13:50, Yueqi Li wrote:
> >
> > Hi,
> >
> > I'm unable
Hi,
I'm unable to access *trac.sagemath.org *tonight. I'm wondering if is the
website down?
Best,
Nicole Yueqi
--
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
https://downforeveryoneorjustme.com/trac.sagemat.org
says it’s not just you or me.
> On 15/04/2022, at 13:50, Yueqi Li wrote:
>
> Hi,
>
> I'm unable to access trac.sagemath.org. I'm wondering if it's because the
> website down?
>
> Sincerely,
> Nicole
>
> --
> You received this message
You do realise that those files under sage/build/pkgs and sage/pkgs are
actually symlinks to a single instance?
> On 15/04/2022, at 12:25, John H Palmieri wrote:
>
> I think your search is following some symbolic links: only three of these
> instances are under version control (git):
>
>
Hi,
I'm unable to access *trac.sagemath.org. *I'm wondering if it's because the
website down?
Sincerely,
Nicole
--
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
Sorry, I should have added: I'm using 9.6.beta5 on MacOS Monterey v. 12.2.
On Thursday, April 14, 2022 at 8:17:11 PM UTC-5 Trevor Karn wrote:
> Hi all,
>
> I have tried to create a nice image of a Hasse diagram (of the set
> partitions of {1,2,3,4}) using the command
Hi all,
I have tried to create a nice image of a Hasse diagram (of the set
partitions of {1,2,3,4}) using the command `view(Poset((SetPartitions(4),
lambda A,B: A in B.refinements(`
as suggested in these notes by Mike Zabrocki
I think your search is following some symbolic links: only three of these
instances are under version control (git):
% git grep 'resolvelinks()'
sage:resolvelinks() {
src/bin/sage:resolvelinks() {
src/bin/sage-env:resolvelinks() {
The last one should probably have a comment in
Hi,
Personally, I would rather see the time spent investigating whether or
not we truly need the symlink-free path in the instances where
resolvelinks() is currently used. I would guess not -- that there is a
better solution to whatever other problem prompted the resolvelinks()
function. But I
Hi,
> VS code cannot debug python code that is executed by a shell script.
It looks like he has set the expectation too high.
> My strategy usually is to create a new (temporary) python file that
contains the code I want to debug (or calls the method I want to debug),
and then use the python
On Thu, Apr 14, 2022 at 12:15 PM Jaap Spies wrote:
>
> Excellent idea! For me it was good in the early years of sage to contribute
> some code and
> give some financial support in the form of the Spies Prize. I'm not in the
> position now to lineup
> as a donor, but I probably will for the 2022
Excellent idea! For me it was good in the early years of sage to contribute
some code and
give some financial support in the form of the Spies Prize. I'm not in the
position now to lineup
as a donor, but I probably will for the 2022 version.
Best regards,
Jaap Spies
On Wednesday, April 13,
VS code cannot debug python code that is executed by a shell script. You
have to execute python code directly in order to debug it. My strategy
usually is to create a new (temporary) python file that contains the code I
want to debug (or calls the method I want to debug), and then use the
The config.log that you sent does not correspond to this build.
It comes from a run of "configure" that ended with the error:
"configure:10277: error: Cannot build Sage on macOS with GNU's gcc. Make
use gcc and g++ are actually Clang compilers."
So what needs to be done here is to clean up PATH.
I volunteer.
John
On Thu, 14 Apr 2022, 16:10 William Stein, wrote:
> I also volunteer to be on the committee.
>
> On Thu, Apr 14, 2022 at 2:01 AM Samuel Lelievre
> wrote:
> >
> > Excellent idea. I volunteer to be on the committee. --Samuel
> >
> > --
> > You received this message because you
I also volunteer to be on the committee.
On Thu, Apr 14, 2022 at 2:01 AM Samuel Lelievre
wrote:
>
> Excellent idea. I volunteer to be on the committee. --Samuel
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this
Excellent idea. I volunteer to be on the committee. --Samuel
--
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
18 matches
Mail list logo
