Re: [sage-devel] Oooold tickets
> There is even 8 tickets older than one year waiting for review. > > I don't know if they are a problem or not. They will make harder to find > "real" todo-lists -- but then, who is going to go throught wishlists in any > case? I also occasionally go through old tickets, complaining internally about forgotten ones, but I have found no magic to deal with them. Sage is very wide, and I don't understand half of the code -- the best I ever aimed for was to do something for those of the tickets I actually understood. If you get what is inside then try to reiew it, and if you know someone who could send him an email, asking for his help and hoping that something will happen. If those who can do the job are aware of it, well, there isn't much more that can be done :-/ Nathann -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Jupyter notebook by default?
On Mon, Jan 4, 2016 at 10:21 AM, kcrisman wrote: > Thank you Jonathan for clarifying what I thought was obvious in what I was > saying. > > >> > As stated, that would break the compatibility with SMC magics that >> William >> > just declared intangible (and always "cell magic"). >> >> Just to be clear: I don't care whether or not whatever design you >> guys are coming up with in this thread is compatible with SMC Sage >> worksheets. SMC provides both Sage worksheets and Jupyter notebooks >> on an equal footing; each has its pros and cons, and will continue to >> be fully supported (likely with a converter between them, that at >> least converts what can be converted). >> >> > I would be interested in why SMC provides Sage worksheets if Jupyter is so > *clearly* the most superior option. [Rhetorical question] > Weird question, given that I literally just wrote "Sage worksheets and Jupyter notebooks on an equal footing; each has its pros and cons, and will continue to be fully supported". There are many ways in which Sage worksheets are superior to Jupyter notebooks, and some very nontrivial subtle new things I've been working on the last month that will lead to more... > > And what of the long-term in Sage itself - would an eventual "SMC personal > edition" become the default? [Not rhetorical but probably too far in the > future to speculate] > No clue. There's no legal or technical reason it couldn't happen... This year it likely won't as SMC is still changing way too much. -- William > -- > 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 post to this group, send email to sage-devel@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. > -- William (http://wstein.org) -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Re: Jupyter notebook by default?
Thank you Jonathan for clarifying what I thought was obvious in what I was saying. > > As stated, that would break the compatibility with SMC magics that > William > > just declared intangible (and always "cell magic"). > > Just to be clear: I don't care whether or not whatever design you > guys are coming up with in this thread is compatible with SMC Sage > worksheets. SMC provides both Sage worksheets and Jupyter notebooks > on an equal footing; each has its pros and cons, and will continue to > be fully supported (likely with a converter between them, that at > least converts what can be converted). > > I would be interested in why SMC provides Sage worksheets if Jupyter is so *clearly* the most superior option. [Rhetorical question] And what of the long-term in Sage itself - would an eventual "SMC personal edition" become the default? [Not rhetorical but probably too far in the future to speculate] -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] Oooold tickets
On Mon, 4 Jan 2016, Daniel Krenn wrote: what is the plan for/status of - - The last activity there is 10 (and 7) month ago. It is not at all uncommon for a ticket to be forgotten. At http://trac.sagemath.org/report/58 you will see a big list of those. As a trivial example, two weeks ago I suggested closing http://trac.sagemath.org/ticket/10783 that had last modification five years ago. There is even 8 tickets older than one year waiting for review. I don't know if they are a problem or not. They will make harder to find "real" todo-lists -- but then, who is going to go throught wishlists in any case? -- Jori Mäntysalo
Re: [sage-devel] lazy list tickets
On 2016-01-04 18:14, Nathann Cohen wrote: >> what is the plan for/status of http://trac.sagemath.org/ticket/16137 >> (and related tickets, e.g. >> http://trac.sagemath.org/ticket/16107 ) ? >> The last activity there is 10 (and 7) month ago. > > The technical terminology is "forgotten". :) > Why don't you ask on the tickets directly, so that the guys in Cc > receive an email? There are a couple of these tickets, so I decided to ask here. However, I will do it on the ticket #16137 now. Daniel -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
Re: [sage-devel] lazy list tickets
> what is the plan for/status of http://trac.sagemath.org/ticket/16137 > (and related tickets, e.g. > http://trac.sagemath.org/ticket/16107 ) ? > The last activity there is 10 (and 7) month ago. The technical terminology is "forgotten". Why don't you ask on the tickets directly, so that the guys in Cc receive an email? Nathann -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] lazy list tickets
Dear all, what is the plan for/status of http://trac.sagemath.org/ticket/16137 (and related tickets, e.g. http://trac.sagemath.org/ticket/16107 ) ? The last activity there is 10 (and 7) month ago. Best, Daniel -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
[sage-devel] Re: patchbot hera-optiplex
Hi,
I confirm that the patchbot hera-OptiPlex-7010 misbehaves: it
systematically returns "build failed" with the message
The content of "/home/hera/sage-patchbot/build/pkgs/r_jupyter/type" must be
'base', 'standard', 'optional', 'experimental' or 'pip'
Apply -- 4 seconds
Traceback (most recent call last):
File "/home/hera/sage-patchbot/local/bin/patchbot/patchbot.py", line 940, in
test_a_ticket
do_or_die('./configure')
File "/home/hera/sage-patchbot/local/bin/patchbot/util.py", line 182, in
do_or_die
raise exn_class("{} {}".format(res, cmd))
Exception: 256 ./configure
in the manifolds tickets, see e.g.
http://patchbot.sagemath.org/ticket/18529/
Eric.
--
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 post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
