Re: [sage-devel] source code comments: doctesting instructions

[kcrisman]

>
>
> >> That's what 
> >> 
> >> # long time 
> >> 
> >> is supposed to be for. 
> > 
> > I don't think so. You wouldn't want to see a doctest take one hour to 
> > run, even if it is flagged with 'long time'. I don't know about you, 
> > but I run 'long' doctests several time per day on some files. 
> > 

If you have tests that take too long, then we need another tag "# really 
> long". 
>  


Maybe we really do, since I can remember a number of tickets where tests 
were removed or changed from the most useful versions because even the 
"long" tests were running more than X seconds in the file (for a smallish 
value of X, not 3600 or something).  Then at least one could run the really 
long tests before a stable release.  But many of those really do have great 
value for users even if it is impractical to run them every time tests are 
run. 

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: Error installing package mpir-2.7.0 on arch linux

[Bill Hart]

Unfortunately I'm unable to help with this. It looks like a Sage/toolchain 
issue which I'm afraid someone else will have to sort out. I don't have any 
ideas at all.

Bill.

On Sunday, 1 November 2015 21:31:39 UTC+1, pang wrote:
>
> mpir 2.7.0 compiled just fine using the AUR package. I didn't 'pacman 
> -Syu' in between.
>
> My previous sage installed upgraded to sage 6.9 with no problem, and 
> version is 2.7.0, but there was a system upgrade in between.
>
> I don't need to solve this, but I will perform other attempts if it can 
> help in any way.
>
> Actually, I just wanted to build a clean sage to check a certain bug I got.
>
> Regards
>
> El 31/10/15 a las 22:41, Bill Hart escribió:
> > > Hi, > > I'm one of the MPIR developers. I am unable to find any 
> information on this issue. And Arch Linux seems to have a working 
> MPIR-2.7.0 package which doesn't require any specific patching: > > 
> https://aur.archlinux.org/packages/mpir/ > > My guess is something 
> unusual with your system, or a recent change in Arch Linux that breaks 
> things. > > Either way, it is not clear I can really help. > > Can you 
> verify whether this is a Sage/toolchain or an MPIR issue by downloading 
> MPIR-2.7.0 from http://www.mpir.org and trying to build it on your system 
> (./configure; make; make check). > > Bill. > > On Friday, 30 October 2015 
> 09:43:21 UTC+1, pang wrote: > > Hello, I just got an error trying to 
> compile sage 6.9 from source, on a just updated archlinux with kernel 
> 4.2.3. > > A couple of days ago I could upgrade my working 
> installation, and it worked, but it failed at building the documentation. > 
> > Regards > > | > libtool:compile: gcc -DHAVE_CONFIG_H 
> -I.-I..-D__GMP_WITHIN_GMP -I..-m64 -O2 -march=core2 -mtune=core2 -g -c 
> sqrt.c  -fPIC -DPIC -o .libs/sqrt.o > Infile included fromsqrt.c:24:0: 
> > ../mpir.h:1165:63:error:expected ')'before '||'token >  
> __GMP_DECLSPEC voidmpz_sub_ui __GMP_PROTO ((mpz_ptr,mpz_srcptr,mpir_ui)); 
> >^ 
> > ../mpir.h:328:24:note:indefinition of macro '__GMP_PROTO' >  
> #define__GMP_PROTO(x)x > ^ > Infile 
> included from/usr/include/features.h:365:0, >  
> from/usr/include/stdio.h:27, >  fromsqrt.c:23: > 
> ../mpir.h:1175:39:error:unknown type name 'wchar_t' >  __GMP_DECLSPEC 
> voidmpz_submul_ui __GMP_PROTO ((mpz_ptr,mpz_srcptr,mpir_ui)); 
> >^ > 
> ../mpir.h:1178:44:error:unknown type name 'wchar_t' >  __GMP_DECLSPEC 
> voidmpz_swap __GMP_PROTO ((mpz_ptr,mpz_ptr))__GMP_NOTHROW; 
> > ^ > 
> ../mpir.h:1179:16:error:unknown type name 'wchar_t' > Infile included 
> fromsqrt.c:24:0: > ../mpir.h:1196:2:error:#endifwithout #if >  
> __GMP_DECLSPEC mpir_ui mpz_tdiv_qr_ui __GMP_PROTO 
> ((mpz_ptr,mpz_ptr,mpz_srcptr,mpir_ui)); >   ^ > 
> ../mpir.h:1205:14:error:unknown type name 'wchar_t' >  __GMP_DECLSPEC 
> mpir_ui mpz_tdiv_r_ui __GMP_PROTO ((mpz_ptr,mpz_srcptr,mpir_ui)); 
> >   ^ > ../mpir.h:1212:27:error:unknown type name 
> 'wchar_t' > ../mpir.h:1216:28:error:unknown type name 'wchar_t' >  
> #definempz_urandomm __gmpz_urandomm > ^ 
> > ../mpir.h:1217:14:error:unknown type name 'wchar_t' >  
> __GMP_DECLSPEC voidmpz_urandomm __GMP_PROTO 
> ((mpz_ptr,gmp_randstate_t,mpz_srcptr)); >   ^ > 
> ../mpir.h:1222:1:error:expected identifier or'('before numeric constant 
> > Infile included from/usr/include/features.h:365:0, 
> >  from/usr/include/stdio.h:27, >  
> fromsqrt.c:23: > ../mpir.h:1228:40:error:unknown type name 'wchar_t' 
> > ../mpir.h:1231:45:error:unknown type name 'wchar_t' > 
> ../mpir.h:1232:17:error:unknown type name 'wchar_t' >  __GMP_DECLSPEC 
> uintmax_t mpz_get_ux __GMP_PROTO ((mpz_srcptr)); >  ^ 
> > Infile included fromsqrt.c:24:0: > ../mpir.h:1259:8:error:unknown 
> type name 'wint_t' >  #definempq_add __gmpq_add > ^ > 
> ../mpir.h:1260:8:error:unknown type name 'wint_t' >  __GMP_DECLSPEC 
> voidmpq_add __GMP_PROTO ((mpq_ptr,mpq_srcptr,mpq_srcptr)); > ^ 
> > ../mpir.h:1266:8:error:unknown type name 'wint_t' >  
> __GMP_DECLSPEC voidmpq_clear __GMP_PROTO ((mpq_ptr)); > ^ > 
> ../mpir.h:Infunction'__gmpz_set_q': > 
> ../mpir.h:2047:3:warning:implicitdeclaration of 
> function'mpz_tdiv_q'[-Wimplicit-function-declaration] >  #endif 
> >^ > ../mpir.h:Infunction'mpq_abs': > 
> ../mpir.h:2070:5:warning:implicitdeclaration of function > | > ... 
> > > -- > You received this message because you are subscribed to a topic in 
> the Google Groups "sage-devel" group. > To 

[sage-devel] [sage-nt] Review of tickets #17909, #17943, #18043

[Jonas Jermann]

Hi all

I already sent this to sage-nt but didn't get a response, so I try 
again: Can someone maybe have a look at one of the tickets above

(in particular  #17909)?

They are for modular forms for Hecke triangle groups.
In particular this includes (classical) modular forms for SL2(Z)
and for the Theta subgroup (see the readme for more information).

I no longer work in academics (I'm a software developer now)
but the code might be useful for others (e.g. in the classical cases) 
and in my opinion it would be a pity if the functionality got lost in

the ticket graveyard...

I didn't expect a fast review but the tickets are there since
quite a while already... :-)

#17909: Rankin Cohen brackets (also for quasi forms) and more
decomposition methods for quasi forms

#17943: Depends on #17909 (but I could make it separate I guess).
Here I tried to make some experimental code (conversions
from numerical coefficients to exact forms) more robust
and fixed some bugs

#18043: I tried my best to add support for HyperbolicPlane(), it could
certainly be improved by someone familiar with the
HyperbolicPlane code...

So if someone has time or is interested, it's appreciated. :-)


Best
Jonas



PS
I would be interested in generalizing the implementation to Jacobi
forms if someone has the time to help me with the algebraic structure.

PPS
Using appropriate subspaces it's quite easy to find some differential 
equations satisfied by the forms (e.g. E2). For instance I found:

n=4
E2.derivative(4) == -3/2*E2^2*E2.derivative(2) + 5/2*E2*E2.derivative(3) 
+ 9/4*E2*E2.derivative()^2 -3*E2.derivative()*E2.derivative(2)

n=5 (non-arithmetic)
E2^3*E2.derivative(2) == E2^2*E2.derivative(3) + 3/2 * 
E2^2*E2.derivative()^2 + 4*E2*E2.derivative()*E2.derivative(2) -20/3 * 
E2.derivative()*E2.derivative(3) -22/3*E2.derivative()^3 + 
40/9*E2.derivative(2)^2

Maybe that's of interest to someone...

--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Satellite Sage Days in January 2016 in Seattle?

[William Stein]

Hi Sage Developers,

Who is interested in a Sage Days adjacent to the Joint Math Meetings
in January 2016 in Seattle?  I have funding for US citizens.  And I
live in Seattle.

 -- William

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: sagemath 6.9 Ubuntu PPA: Error typesetting mathematics

[Jan Groenewald]

Hi

This might be a leftover error from a previous versio nwhen mathjax moved.
Please try

sudo -i
cd
/usr/lib/sagemath/local/lib/python2.7/site-packages/sagenb-0.11.4-py2.7.egg/sagenb/data/
rm -rf mathjax
ln -s ../../../../../../share/mathjax/

Or inspect first whether that symlink is there already?

If it is actually a PPA error (I doubt it, I think we fixed in 6.6) we will
look at uploading a fix.

Regards,
Jan

On 2 November 2015 at 20:22, Samuel Lelièvre 
wrote:

> Follow-up: When I launch the Jupyter notebook, I get this warning:
>
> """
> Failed to retrieve MathJax from '../nbextensions/mathjax/MathJax.js'
>
> Math/LaTeX rendering will be disabled.
>
> If you have administrative access to the notebook server and a working
> internet connection, you can install a local copy of MathJax for
> offline use with the following command on the server at a Python or
> Jupyter prompt:
>
> >>> from Jupyter.external import mathjax; mathjax.install_mathjax()
>
> This will try to install MathJax into the Jupyter source directory.
>
> If Jupyter is installed to a location that requires administrative
> privileges to write, you will need to make this call as an
> administrator, via 'sudo'.
>
> When you start the notebook server, you can instruct it to disable
> MathJax support altogether:
>
> $ ipython notebook --no-mathjax
>
> which will prevent this dialog from appearing.
> """
>
>
>
> 2015-11-02 19:21 GMT+01:00 Samuel Lelièvre :
> > Hi,
> >
> > On the "SageMath 6.9" Ubuntu PPA, installed in the computer rooms
> > in my department, I started Sage, then typed
> >
> > sage: notebook()
> >
> > to get the Sage Notebook. I open a new worksheet and type
> >
> > 7*7
> >
> > and shift-enter to evaluate. I get the following output:
> >
> > Error typesetting mathematics
> > 49
> >
> > Actually, every output starts by "Error typesetting mathematics",
> > including graphic output.
> >
> > It looks very similar to what happened with the "SageMath 6.6"
> > Ubuntu PPA:
> > https://groups.google.com/d/topic/sage-devel/nESRhwQ0wSU/discussion
> >
> > Does it point to some problem with the MathJax install?
> > Are you planning to release a fixed SageMath 6.9 PPA?
> >
> > Best,
> > Samuel
>



-- 
  .~.
  /V\ Jan Groenewald
 /( )\www.aims.ac.za
 ^^-^^

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] source code comments: doctesting instructions

[Nathann Cohen]

> Maybe we really do, since I can remember a number of tickets where tests
> were removed or changed from the most useful versions because even the
> "long" tests were running more than X seconds in the file (for a smallish
> value of X, not 3600 or something).  Then at least one could run the really
> long tests before a stable release.  But many of those really do have great
> value for users even if it is impractical to run them every time tests are
> run.

Hm It was once suggested (maybe by Jeroen?) that we could
have, for free, a decorator like that. Something like '# optional -
veryverylong'. Just add whatever tag you want after an 'optional' and
it will work.

There are some tests that I run 'from time to time', especially in a
development phase (while a big module is being written) to make sure
that all results stay correct. To take the example of Strongly Regular
Graphs (SRG) that Jori mentionned, I run from time to time a script
that builds them all up to n=2000 (the same was done on combinatorial
designs). That's something I run to double-check what I do, but I
would feel guilty if I forced anybody but me to run it regularly.

I don't know how such a type of test could be named, or whether this
name should be 'standard'. Just writing this to explain my situation,
in case it makes more sense to somebody else :-)

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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: git on xkcd

[Volker Braun]

Also fun: The git man-page 
generator http://git-man-page-generator.lokaltog.net/


On Saturday, October 31, 2015 at 4:00:39 AM UTC+1, kcrisman wrote:
>
> http://xkcd.com/1597/
>

-- 
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] source code comments: doctesting instructions

[Jeroen Demeyer]

On 2015-10-30 08:35, Jori Mäntysalo wrote:

- Be better developer with sort(result) or something similar


This option has my vote because it's the most explicit. We shouldn't 
allow the doctest framework to behave too much different from an 
interactive session, so I'm not in favour of behind-the-scenes sorting.


Jeroen.

--
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 http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.