Re: [sage-devel] Re: ModuleNotFoundError: No module named 'sage'

2022-05-01 Thread Matthias Koeppe
On Saturday, April 30, 2022 at 10:59:59 PM UTC-7 hohoa...@gmail.com wrote: > > > Open a ticket, push a branch... > The mechanics of this operation is currently beyond this hitchhiker. When > it is needed, she will need help. > (It seems pushing broken code is not a good idea to her. Is there any

Re: [sage-devel] Re: ModuleNotFoundError: No module named 'sage'

2022-05-01 Thread ph h
Hi, Thank you for your response. > This also seems like a lot of work to eliminate some minor code duplication Besides being error prone (in maintaining duplicates), it seems to start small with just 'resolvelinks', then the whole files ('sage', 'sage-env'), then whole directories? Furthermore, t

Re: [sage-devel] orbit decompositions

2022-05-01 Thread 'Travis Scrimshaw' via sage-devel
> > Sorry, I don't know an easy way. I've always just defined them by hand >> whenever needed. >> However, I agree with you that a better way is needed. >> > > I would love for there to be some standard way to define a group action on > a set - preferably maintaining other algebraic properties

[sage-devel] Re: Memory Leak in canonical_label with bliss?

2022-05-01 Thread 'Travis Scrimshaw' via sage-devel
Hi Thomas, Sorry for taking so long to respond as I was away from my computer last week to test. Yes, I seem to be seeing it as well. However, if it is within bliss, then it needs to be solved upstream (and/or with a patch here). Best, Travis On Tuesday, April 26, 2022 at 5:47:07 AM UTC+9

Re: [sage-devel] Warnings about the current development version are greatly exaggerated

2022-05-01 Thread Matthias Koeppe
This is now https://github.com/sagemath/website/pull/246 On Sunday, May 1, 2022 at 12:45:05 PM UTC-7 François Bissey wrote: > This is sage-devel, most people here eat sage unstable for breakfast, may > be ask in sage-support? But otherwise, yes it is overly scary. It may have > been justified 1

Re: [sage-devel] Warnings about the current development version are greatly exaggerated

2022-05-01 Thread François Bissey
This is sage-devel, most people here eat sage unstable for breakfast, may be ask in sage-support? But otherwise, yes it is overly scary. It may have been justified 10 years ago but not so much now. > On 2/05/2022, at 07:19, Matthias Koeppe wrote: > > https://www.sagemath.org/download-latest.ht

Re: [sage-devel] Warnings about the current development version are greatly exaggerated

2022-05-01 Thread William Stein
On Sun, May 1, 2022 at 12:19 PM Matthias Koeppe wrote: > https://www.sagemath.org/download-latest.html shows a very scary warning > "Unstable release for development only. Do *not* use for your every day > work." > > Would there be objections to toning this down a bit? > +1 great idea! > > --

[sage-devel] Warnings about the current development version are greatly exaggerated

2022-05-01 Thread Matthias Koeppe
https://www.sagemath.org/download-latest.html shows a very scary warning "Unstable release for development only. Do *not* use for your every day work." Would there be objections to toning this down a bit? -- You received this message because you are subscribed to the Google Groups "sage-deve

[sage-devel] Sage Dev Prizes

2022-05-01 Thread William Stein
Hello Sage-Devel, The 3 people who expressed interest in being on the Sage dev prize committee are me, John Cremona, and Karl-Dieter Crisman. Would anybody else like to be on the committee? Are there any objections to the people currently on the committee? Also, are there any nominations for go

Re: [sage-devel] Re: ModuleNotFoundError: No module named 'sage'

2022-05-01 Thread Matthias Koeppe
On Saturday, April 30, 2022 at 10:59:59 PM UTC-7 hohoa...@gmail.com wrote: > $SAGE_ROOT/src/bin: > >- sage.src.bin.resolvelinks.dot (factored out from >*'sage-env')* >- sage.src.bin.sage-env.dot (factored out from >*'sage-env')* >- sage.src.bin.sage-env.

Re: [sage-devel] Re: ModuleNotFoundError: No module named 'sage'

2022-05-01 Thread John H Palmieri
You can run "git diff" and save the results in a file, and then post a link to the file. Then others could apply the patch and try it out. This also seems like a lot of work to eliminate some minor code duplication, in my opinion. On Saturday, April 30, 2022 at 10:59:59 PM UTC-7 hohoa...@gmail.