On Tue, Aug 28, 2018 at 2:36 AM John Cremona <john.crem...@gmail.com> wrote: > > I could do this for elliptic curves, but not this week as I'm at a meeting.
FWIW for elliptic curves my python3 branch has these failures: sage -t src/sage/schemes/elliptic_curves/descent_two_isogeny.pyx # 1 doctest failed sage -t src/sage/schemes/elliptic_curves/cm.py # 4 doctests failed sage -t src/sage/schemes/elliptic_curves/ell_modular_symbols.py # 4 doctests failed sage -t src/sage/schemes/elliptic_curves/ell_rational_field.py # 3 doctests failed sage -t src/sage/schemes/elliptic_curves/isogeny_class.py # 4 doctests failed sage -t src/sage/schemes/elliptic_curves/padic_lseries.py # 1 doctest failed sage -t src/sage/schemes/elliptic_curves/gal_reps_number_field.py # 2 doctests failed sage -t src/sage/schemes/elliptic_curves/ell_number_field.py # 2 doctests failed sage -t src/sage/schemes/elliptic_curves/constructor.py # 1 doctest failed So, fewer, but still a number. What this means in part of course is that I still need to get more python3 fixes upstreamed and merged. I'll have more time after the OpenDreamKit reporting period is over. > On Mon, 27 Aug 2018 at 00:02, John H Palmieri <jhpalmier...@gmail.com> wrote: >> >> 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 >>> <module> >>> 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 # 193 doctests >>> failed >>> sage -t --long src/sage/modular/abvar/homspace.py # 121 doctests failed >>> sage -t --long src/sage/modular/modsym/space.py # 292 doctests failed >>> sage -t --long src/sage/modular/hecke/submodule.py # 138 doctests failed >>> sage -t --long src/sage/modular/modform/space.py # 216 doctests failed >>> sage -t --long src/sage/schemes/toric/divisor.py # 272 doctests failed >>> sage -t --long src/sage/schemes/toric/variety.py # 384 doctests failed >>> sage -t --long src/sage/combinat/constellation.py # 203 doctests failed >>> sage -t --long src/sage/combinat/finite_state_machine.py # 207 doctests >>> failed >>> sage -t --long src/sage/schemes/toric/morphism.py # 282 doctests failed >>> sage -t --long src/sage/modular/pollack_stevens/space.py # 133 doctests >>> failed >>> sage -t --long src/sage/geometry/fan.py # 238 doctests failed >>> sage -t --long src/sage/combinat/words/finite_word.py # 189 doctests failed >>> sage -t --long src/sage/modular/hecke/module.py # 158 doctests failed >>> sage -t --long src/sage/schemes/toric/fano_variety.py # 132 doctests failed >>> sage -t --long src/sage/modular/abvar/finite_subgroup.py # 150 doctests >>> failed >>> sage -t --long src/sage/geometry/fan_morphism.py # 223 doctests failed >>> sage -t --long src/sage/schemes/toric/toric_subscheme.py # 128 doctests >>> failed >>> sage -t --long src/sage/rings/valuation/limit_valuation.py # 106 doctests >>> failed >>> sage -t --long src/sage/schemes/toric/points.py # 161 doctests failed >>> sage -t --long src/sage/modular/modsym/boundary.py # 161 doctests failed >>> sage -t --long src/sage/modular/abvar/morphism.py # 166 doctests failed >>> sage -t --long src/sage/rings/padics/factory.py # 104 doctests failed >>> >>> >>> >> -- >> 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. -- 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.