[sage-devel] Customizin failed login -page
See https://sage.sis.uta.fi/ . I just learnt that our students do not see the text "This is part of services available to students of SIS unit. To get an account see (link)this page(/link)." A wish for those making frontend(s) to SageMath: please make it easy to customize failed login -page. -- Jori Mäntysalo
[sage-devel] DeprecationWarning stacklevel issues
Consider the following code
def g():
function("f", x)
html(04)
g()
which in SageMathCell gives the following warning messages (in Sage itself
and SageMathCloud everything is even more useless without using an extra
module due to
https://groups.google.com/d/topic/sage-devel/-KiMrG--5x8/discussion ):
sagemathcell.py:5: DeprecationWarning: Calling function('f',x) is deprecated.
Use function('f')(x) instead.
See http://trac.sagemath.org/17447 for details.
g()
sagemathcell.py:5: DeprecationWarning: use 0o as octal prefix instead of 0
If you do not want this number to be interpreted as octal, remove the leading
zeros.
See http://trac.sagemath.org/17413 for details.
g()
sagemathcell.py:3: DeprecationWarning: html(...) will change soon to return
HTML instead of printing it. Instead use pretty_print(html(...)) for strings or
just pretty_print(...) for math.
See http://trac.sagemath.org/18292 for details.
html(04)
The problem is - the first two messages go too far in the call stack and
complain about a wrong piece of code, which is very confusing in longer
examples. It may have something to do with Cython involved in dealing with
symbolic functions and numbers.
The question is - what is the proper way to fix it??? Using different
stacklevels on a case-by-case basis is too error-prone, so hopefully
something automatic can be done in the deprecation function itself.
Thank you!
Andrey
--
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: puzzling dev.upload_ssh_key() in developer manual
On Sunday, October 16, 2016 at 8:56:56 AM UTC, B Krishnan Iyer wrote: > > Hello, > > Understood, I been to that link earlier and it really helps but in future > if you are starting a project on more advanced feature(previous feature > included too) then I will be very interested in taking part. > Starting a project? Why must it be a new project? If you like, you can well work on this feature of git-trac yourself, submit pull requests with your improvements, etc. > Thank you, > -- 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: Make OpenBLAS Error
Wasn't stated in the build instructions. On Thursday, October 13, 2016 at 5:03:20 AM UTC-4, François wrote: > > Not spending the time compiling gcc to get gfortran? > > François > > > On 13/10/2016, at 22:01, Sébastien Labbé > > wrote: > > > > > > > > On Wednesday, October 12, 2016 at 9:07:24 PM UTC+2, Eric Gourgoulhon > wrote: > > > with Ubuntu 16.04, if you install the Ubuntu package gfortran-5, your > Sage build will use the system gfortran, which works fine (no missing > libgfortran.so.3). > > > > Is there any other reason/advantage for Sage to use the system gfortran? > > > > Sébastien > > > > -- > > 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+...@googlegroups.com . > > To post to this group, send email to sage-...@googlegroups.com > . > > Visit this group at https://groups.google.com/group/sage-devel. > > For more options, visit https://groups.google.com/d/optout. > > -- 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] Make OpenBLAS Error
I'll make sure to continue to do so in the future if I see those messages! I usually zone out during builds, glad I caught that line. Thanks for the help. On Thursday, October 13, 2016 at 2:14:37 AM UTC-4, Jeroen Demeyer wrote: > > On 2016-10-12 18:14, Ethan Petersen wrote: > > there was an "Error building OpenBLAS"/"Error installing package > openblas-0.2.19" with a suggestion to email this google group with the > attached log file. > > I'm glad that you did that! Almost *nobody* seems to read that message. > > > If anyone has ideas on solving this issue, please let me know! > > There is a fix at https://trac.sagemath.org/ticket/21689 but it's not > yet in a Sage release. > -- 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: Make OpenBLAS Error
Thanks Steven, this worked great for me. Now just have to make sure the rest of the make goes well. On Wednesday, October 12, 2016 at 1:40:57 PM UTC-4, Steven Trogdon wrote: > > It looks like you are missing libgfortran3 libraries or at least they > could not be found. Perhaps > > apt-get install libgfortran3 > > but there could be something else that's the problem. > > On Wednesday, October 12, 2016 at 11:43:20 AM UTC-5, Ethan Petersen wrote: >> >> Hello all, >> >> I'm building sage on a Lenovo Thinkpad W540 with Ubuntu 16.04, and there >> was an "Error building OpenBLAS"/"Error installing package openblas-0.2.19" >> with a suggestion to email this google group with the attached log file. If >> anyone has ideas on solving this issue, please let me know! >> >> Thanks, >> >> Ethan >> > -- 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: Make OpenBLAS Error
Hi Eric, Thanks for clearing this up, appreciate your reply! Ethan On Wednesday, October 12, 2016 at 3:07:24 PM UTC-4, Eric Gourgoulhon wrote: > > Hi, > > Just to complete Steven's answer: with Ubuntu 16.04, if you install the > Ubuntu package gfortran-5, your Sage build will use the system gfortran, > which works fine (no missing libgfortran.so.3). In this case, you do not > need the fix introduced in https://trac.sagemath.org/ticket/21689 > > Best wishes, > > 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.
[sage-devel] Re: puzzling dev.upload_ssh_key() in developer manual
Hello, Understood, I been to that link earlier and it really helps but in future if you are starting a project on more advanced feature(previous feature included too) then I will be very interested in taking part. Thank you, -- 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: puzzling dev.upload_ssh_key() in developer manual
On Sunday, October 16, 2016 at 5:39:29 AM UTC, B Krishnan Iyer wrote: > > Hello, > > I think removing that content from the doc isn't the solution. I thinking > we should work on a feature like this yet it has proof of being useful so > it justify its need. > well, the feature is gone, and the documentation has to adjusted. A better place for such a feature would be git-trac extension, see https://github.com/sagemath/git-trac-command (IIRC there was already a discussion on this, at it was agreed to be the more proper place) > > Thank you, > -- 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.
