Re: [sage-devel] Re: New code to generate finite lattices
On Sat, 25 Aug 2018, 'Martin R' via sage-devel wrote: That would be great! (in particular, if it's fast :-) Seems to be fast. First step would be that someone test the code with Mac OS X and Cygwin. (Of course the slowest part is converting data to Sage. So if we want to generate, say, planar lattices, it is much faster if we do the filtering in C-phase. For graded, semimodular and modular lattices we could even make the generating part in C.) -- Jori Mäntysalo
[sage-devel] Re: doctest in sage/repl/load.py broken due to http://wstein.org/loadtest.py
Hi, I think that's due to some scraping protection by cloudflare. However,
this file doesn't need to be there and I've put it in the "files"
subdirectory of the website. I think that's a robust location and suiteable
for this. E.g. here I'm downloading it via curl in linux, which I assume
should work from within sage, too
$ curl https://www.sagemath.org/files/loadtest.py
print "hi from the net"
print 2+3
I've no idea what "test.sobj" is.
-- harald
On Saturday, August 25, 2018 at 3:23:38 PM UTC+2, Sébastien Labbé wrote:
>
> Hi,
>
> The goal of ticket #25535 is to make the following work:
>
> sage -t --optional=sage,internet src/sage/repl/load.py
>
> There is one issue being the failure of the doctest:
>
> sage: sage.repl.load.load('http://wstein.org/loadtest.py',
> globals()) # optional - internet
>
> Something has changed with that file or with the way to access it because
> it downloads not a Python file but rather an error message html file
> containing expressions like "Access denied | wstein.org used Cloudflare
> to restrict access" and "The owner of this website (wstein.org) has
> banned your access based on your browser's signature.".
>
> See https://trac.sagemath.org/ticket/25535 for details.
>
> William, if you are reading this, do you understand the issue? Can you
> make something on your side to make the doctest work again?
>
> Cheers,
>
> 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+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: doctest in sage/repl/load.py broken due to http://wstein.org/loadtest.py
On Sunday, August 26, 2018 at 1:09:36 PM UTC+2, Harald Schilly wrote:
>
> Hi, I think that's due to some scraping protection by cloudflare. However,
> this file doesn't need to be there and I've put it in the "files"
> subdirectory of the website. I think that's a robust location and suiteable
> for this. E.g. here I'm downloading it via curl in linux, which I assume
> should work from within sage, too
>
> $ curl https://www.sagemath.org/files/loadtest.py
> print "hi from the net"
>
> print 2+3
>
>
> I've no idea what "test.sobj" is.
>
see
http://doc.sagemath.org/html/en/reference/structure/sage/structure/sage_object.html#sage.structure.sage_object.SageObject.save
It's a Sagemath pickle.
I suppose one has to do
create a Sage object that shows as 'hello Sage' (don't know how, though)
sage: s=
sage: s.save('test')
and copy the resulting test.sobj
to an appropriate location with the URL
> -- harald
>
>
> On Saturday, August 25, 2018 at 3:23:38 PM UTC+2, Sébastien Labbé wrote:
>>
>> Hi,
>>
>> The goal of ticket #25535 is to make the following work:
>>
>> sage -t --optional=sage,internet src/sage/repl/load.py
>>
>> There is one issue being the failure of the doctest:
>>
>> sage: sage.repl.load.load('http://wstein.org/loadtest.py',
>> globals()) # optional - internet
>>
>> Something has changed with that file or with the way to access it because
>> it downloads not a Python file but rather an error message html file
>> containing expressions like "Access denied | wstein.org used Cloudflare
>> to restrict access" and "The owner of this website (wstein.org) has
>> banned your access based on your browser's signature.".
>>
>> See https://trac.sagemath.org/ticket/25535 for details.
>>
>> William, if you are reading this, do you understand the issue? Can you
>> make something on your side to make the doctest work again?
>>
>> Cheers,
>>
>> 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+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] python3 report (end of august 2018)
Dear all, here is a short python3 status report. There is a patchbot report with python3 for 8.4.b2 somewhere on the page : https://patchbot.sagemath.org/ticket/0/ (@ patchbot breeders, please update your patchbot so that we know if it builds and runs sage with python2 or python3.) We are now hopefully getting close to making the documentation (html and pdf) build with python3. One good step in this direction would be to merge the 4 waiting pull requests in sagenb (and then upgrade the sagenb spkg, see https://trac.sagemath.org/ticket/25837). Otherwise, some progress has been made on the hash issue (https://trac.sagemath.org/ticket/24551). There remains in particular the controversial question of the hash issue for groups. There is no general agreement on the meaning of equality for groups, and this will probably make the definition of hash difficult. The patchbot report on sage+python3 for 8.4.b2 has still *many* (and I mean *many*) failing doctests. But it also stops badly in the way shown below, complaining that too many files are open. Could somebody investigate this issue, please ? And I would like to know if some buildbot is using the python3 make target that is now available ? Frédéric sage -t --long src/sage/combinat/crystals/kac_modules.py # 3 doctests failed sage -t --long src/sage/matroids/matroids_plot_helpers.py # 1 doctest failed sage -t --long src/sage/libs/gap/element.pyx # 2 doctests failed sage -t --long src/sage/groups/conjugacy_classes.py # 2 doctests failed sage -t --long src/sage/docs/instancedoc.pyx # 1 doctest failed sage -t --long src/sage/rings/padics/factory.py # 104 doctests failed Doctests interrupted: 843/3700 files tested -- Total time for all tests: 6360.5 seconds cpu time: 10897.2 seconds cumulative wall time: 12855.4 seconds Traceback (most recent call last): File "/home/u1/chapoton/sage3/src/bin/sage-runtests", line 156, in err = DC.run() File "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/control.py" , line 1187, in run self.run_doctests() File "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/control.py" , line 915, in run_doctests self.dispatcher.dispatch() File "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/forker.py" , line 1912, in dispatch self.parallel_dispatch() File "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/forker.py" , line 1809, in parallel_dispatch w.start() # This might take some time File "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/forker.py" , line 2095, in start super(DocTestWorker, self).start() File "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/process.py", line 105, in start self._popen = self._Popen(self) File "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/context.py", line 223, in _Popen return _default_context.get_context().Process._Popen(process_obj) File "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/context.py", line 277, in _Popen return Popen(process_obj) File "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/popen_fork.py", line 19, in __init__ self._launch(process_obj) File "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/popen_fork.py", line 65, in _launch parent_r, child_w = os.pipe() OSError: [Errno 24] Too many open files By the way, here are the worst offenders, those having hundreds of failing doctests: sage -t --long src/sage/schemes/elliptic_curves/ell_number_field.py # 107 doctests failed sage -t --long src/sage/modular/pollack_stevens/modsym.py # 199 doctests failed sage -t --long src/sage/schemes/hyperelliptic_curves/ hyperelliptic_finite_field.py # 126 doctests failed sage -t --long src/sage/modular/modform/element.py # 346 doctests failed sage -t --long src/sage/rings/padics/padic_lattice_element.py # 167 doctests failed sage -t --long src/sage/rings/valuation/augmented_valuation.py # 256 doctests failed sage -t --long src/sage/graphs/generic_graph.py # 136 doctests failed sage -t --long src/sage/combinat/partition_kleshchev.py # 116 doctests failed sage -t --long src/sage/dynamics/arithmetic_dynamics/projective_ds.py # 121 doctests failed sage -t --long src/sage/algebras/steenrod/steenrod_algebra.py # 225 doctests failed sage -t --long src/sage/schemes/elliptic_curves/ell_curve_isogeny.py # 214 doctests failed sage -t --long src/sage/combinat/tiling.py # 144 doctests failed sage -t --long src/sage/schemes/toric/sheaf/klyachko.py # 133 doctests failed sage -t --long src/sage/modular/abvar/abvar.py # 606 doctests failed sage -t --long src/sage/modular/modsym/ambient.py # 352 doctests failed sage -t --long src/sage/schemes/toric/chow_group.py # 195 doctests failed sage -t --long src/sage/rings/asymptotic/asymptotic_ring.py
[sage-devel] r-3.4.4.p0 configure/install error
apparently R needs a library called libpaper (you might have noticed the error message about 'paperconf' in the log) Install it, it should work then. -- 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] r-3.4.4.p0 configure/install error
Ah yeah I did notice that. I will try to do that and report back. Thanks! On Sun, Aug 26, 2018, 2:03 PM Dima Pasechnik wrote: > apparently R needs a library called libpaper > (you might have noticed the error message about 'paperconf' in the log) > > Install it, it should work then. > > -- > 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. > -- 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: recommendation: delete local/share/mathjax/mathjax, run make doc-clean, then make
If somehow the bad symlink didn't get created on one machine (you did 'make distclean', for example), but it did on the other, that would probably explain it. On Saturday, August 25, 2018 at 6:39:28 AM UTC-7, Sébastien Labbé wrote: > > On one machine, I get this: > > $ du -s -h local/share/doc/sage > 20G/local/share/doc/sage > > on the other, I get this: > > $ du -s -h local/share/doc/sage > 1,9Glocal/share/doc/sage > > I do not know why the bug affects only one? Thanks for sharing. > > Sébastien > > > On Thursday, August 23, 2018 at 10:13:11 PM UTC+2, John H Palmieri wrote: >> >> I found that my Sage documentation directory was taking up 15GB of hard >> drive space, because of a bug (which I think has been fixed, but I don't >> remember where). The bug was caused by a recursive symlink >> >> local/share/mathjax/mathjax -> local/share/mathjax >> >> When the contents of local/share/mathjax were copied to various _static >> directories in the html documentation, rather than just reproducing the >> symlink, it created many layers of subdirectories; for example, >> ca/intro/_static/mathjax/mathjax/mathjax/... Basically mathjax all the way >> down. I don't know if this happened all at once, or once each time I built >> the documentation. >> >> To see if you have this problem, see if you have the symlink. You might >> also find out how much disk space local/share/doc/sage takes up (for >> example, "du -s -h /path/to/SAGE_ROOT/local/share/doc/sage"). On my >> computer, it is 1.9GB. If you are using up a lot more space than that, you >> might have hit this bug. >> >> To fix: remove the symlink SAGE_ROOT/local/share/mathjax/mathjax. Then >> run "make doc-clean" to remove the old documentation, and then run "make" >> to rebuild the documentation. >> >> Question: >> >> - has the bug been fixed, or is that symlink still being created? >> >> -- >> John >> >> -- 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: python3 report (end of august 2018)
First, thank you, Frédéric, for all of the work you've done on this. Second, to everyone else: if you're an expert in, say, toric varieties or elliptic curves, try building Sage with Python 3 and then fixing doctests on the appropriate directory. Some of these will be easy for anyone, but some may require expertise in the particular mathematics. (Third, by the way, most of the errors in steenrod_algebra.py were fixed by https://trac.sagemath.org/ticket/25927, which already has a positive review. Most of the remaining failures just have to do with different sorting in Python 2 vs. Python 3 when printing dictionaries.) John On Sunday, August 26, 2018 at 8:47:01 AM UTC-7, Frédéric Chapoton wrote: > > Dear all, here is a short python3 status report. > > There is a patchbot report with python3 for 8.4.b2 somewhere on the page : > https://patchbot.sagemath.org/ticket/0/ > (@ patchbot breeders, please update your patchbot so that we know if it > builds and runs sage with python2 or python3.) > > We are now hopefully getting close to making the documentation (html and > pdf) build with python3. One good step in this direction would be to merge > the 4 waiting pull requests in sagenb (and then upgrade the sagenb spkg, > see https://trac.sagemath.org/ticket/25837). > > Otherwise, some progress has been made on the hash issue ( > https://trac.sagemath.org/ticket/24551). There remains in particular the > controversial question of the hash issue for groups. There is no general > agreement on the meaning of equality for groups, and this will probably > make the definition of hash difficult. > > The patchbot report on sage+python3 for 8.4.b2 has still *many* (and I > mean *many*) failing doctests. But it also stops badly in the way shown > below, complaining that too many files are open. Could somebody investigate > this issue, please ? > > And I would like to know if some buildbot is using the python3 make target > that is now available ? > > Frédéric > > sage -t --long src/sage/combinat/crystals/kac_modules.py # 3 doctests > failed > sage -t --long src/sage/matroids/matroids_plot_helpers.py # 1 doctest > failed > sage -t --long src/sage/libs/gap/element.pyx # 2 doctests failed > sage -t --long src/sage/groups/conjugacy_classes.py # 2 doctests failed > sage -t --long src/sage/docs/instancedoc.pyx # 1 doctest failed > sage -t --long src/sage/rings/padics/factory.py # 104 doctests failed > Doctests interrupted: 843/3700 files tested > -- > Total time for all tests: 6360.5 seconds > cpu time: 10897.2 seconds > cumulative wall time: 12855.4 seconds > Traceback (most recent call last): > File "/home/u1/chapoton/sage3/src/bin/sage-runtests", line 156, in > > err = DC.run() > File > "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/control.py" > , line 1187, in run > self.run_doctests() > File > "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/control.py" > , line 915, in run_doctests > self.dispatcher.dispatch() > File > "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/forker.py" > , line 1912, in dispatch > self.parallel_dispatch() > File > "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/forker.py" > , line 1809, in parallel_dispatch > w.start() # This might take some time > File > "/home/u1/chapoton/sage3/local/lib/python3.6/site-packages/sage/doctest/forker.py" > , line 2095, in start > super(DocTestWorker, self).start() > File > "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/process.py", > line 105, in start > self._popen = self._Popen(self) > File > "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/context.py", > line 223, in _Popen > return _default_context.get_context().Process._Popen(process_obj) > File > "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/context.py", > line 277, in _Popen > return Popen(process_obj) > File > "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/popen_fork.py" > , line 19, in __init__ > self._launch(process_obj) > File > "/home/u1/chapoton/sage3/local/lib/python3.6/multiprocessing/popen_fork.py" > , line 65, in _launch > parent_r, child_w = os.pipe() > OSError: [Errno 24] Too many open files > > > By the way, here are the worst offenders, those having hundreds of failing > doctests: > > sage -t --long src/sage/schemes/elliptic_curves/ell_number_field.py # > 107 doctests failed > sage -t --long src/sage/modular/pollack_stevens/modsym.py # 199 doctests > failed > sage -t --long src/sage/schemes/hyperelliptic_curves/ > hyperelliptic_finite_field.py # 126 doctests failed > sage -t --long src/sage/modular/modform/element.py # 346 doctests failed > sage -t --long src/sage/rings/padics/padic_lattice_element.py # 167 > doctests failed > sage -t --long src/sage/r
Re: [sage-devel] python3 report (end of august 2018)
Hi, On 26/08/2018 17:47, Frédéric Chapoton wrote: The patchbot report on sage+python3 for 8.4.b2 has still *many* (and I mean *_many_*) failing doctests. But it also stops badly in the way shown below, complaining that too many files are open. Could somebody investigate this issue, please ? That probably means the doctesting framework is leaking file descriptors, ie: it opens each and every file but never closes them. I would search: (1) either a single piece of code which does all the opening and never closes anything during the whole run (the least likely scenario) (2) or a piece of code forking correct workers (ie: they would open+close correctly) but leaking them (so the closing part doesn't happen) (the most likely scenario). Someone familiar with the code should probably have a look and would be more efficient at spotting the problem. jpuydt on irc.debian.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] r-3.4.4.p0 configure/install error
if you still have the failed Sage install, all you need to do after libpaper installation is to run make again. -- 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.
