Re: [sage-devel] Re: problem with 8.7.beta1
On 2019-01-28 06:18, Travis Scrimshaw wrote: See possibly https://trac.sagemath.org/ticket/27114. No, it's https://trac.sagemath.org/ticket/27109 -- 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: problem with 8.7.beta1
See possibly https://trac.sagemath.org/ticket/27114. On Monday, January 28, 2019 at 6:42:40 AM UTC+10, chris wuthrich wrote: > > Hello > compiling from source for SageMath version 8.7.beta1 on my opensuse leap > 15.0 caused an error after compiling libffi. > > It looks like the problem mentioned at the bottom of #25900. > > It started as > > [libffi-3.2.1] > [libffi-3.2.1] No record that 'libffi' was ever installed; skipping > uninstall > [libffi-3.2.1] Configuring libffi-3.2.1 > [libffi-3.2.1] configure: loading site script > /usr/share/site/x86_64-unknown-linux-gnu > ... > > and then ended with > > ... > [libffi-3.2.1] /usr/bin/install -c -m 644 libffi.pc > '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/inst/usr/local/sage/local/lib/pkgconfig' > [libffi-3.2.1] make[7]: Leaving directory > '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/src/x86_64-unknown-linux-gnu' > [libffi-3.2.1] make[6]: Leaving directory > '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/src/x86_64-unknown-linux-gnu' > [libffi-3.2.1] make[5]: Leaving directory > '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/src/x86_64-unknown-linux-gnu' > [libffi-3.2.1] make[4]: Leaving directory > '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/src' > [libffi-3.2.1] > [libffi-3.2.1] real 0m7.001s > [libffi-3.2.1] user 0m5.834s > [libffi-3.2.1] sys 0m1.524s > [libffi-3.2.1] Copying package files from temporary location > /usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/inst to > /usr/local/sage/local > [libffi-3.2.1] cp: cannot overwrite non-directory > '/usr/local/sage/local/./lib64' with directory > '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/inst/usr/local/sage/local/./lib64' > > /usr/local/sage/local/lib64 is an existing link to > /usr/local/sage/local/lib/ > > full log attached. > > Chris > -- 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 status report
Hi Jeroen, On 2019-01-27, Jeroen Demeyer wrote: > On 2019-01-27 22:36, Simon King wrote: >> But do py3 experts agree that to transform os.path.join(...) to char* >> (which is not in pickling but in module initialisation), I need >> PyString_...? > > No! Please see src/sage/cpython/string.pyx Thank you for the pointer! Best regards, Simon -- 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: python3 status report
On 2019-01-27 22:36, Simon King wrote: But do py3 experts agree that to transform os.path.join(...) to char* (which is not in pickling but in module initialisation), I need PyString_...? No! Please see src/sage/cpython/string.pyx (sorry no time now to answer more) -- 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 status report
PS: On 2019-01-27, Simon King wrote: > The funny thing is that 2 years ago, I was told by Jeroen: > """ > For Python 3 compatibility, you should use bytes instead of str for > pickling. > > This means changing the PyString_... functions to PyBytes_... > """ To be fair, Jeroen talked about pickling, where PyBytes probably still is the way to go. But do py3 experts agree that to transform os.path.join(...) to char* (which is not in pickling but in module initialisation), I need PyString_...? Best regards, Simon -- 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 status report
Hi, On 2019-01-27, Simon King wrote: > Is there a ticket for meataxe on python 3 already? I guess not. So, > unless someone stops me in the next hour or so, I'll open one... I created https://trac.sagemath.org/ticket/27152. First problem: In py2, PyBytes_AsString(os.path.join(DOT_SAGE,'meataxe')) works. In py3 it doesn't, since os.path.join returns str not bytes. The funny thing is that 2 years ago, I was told by Jeroen: """ For Python 3 compatibility, you should use bytes instead of str for pickling. This means changing the PyString_... functions to PyBytes_... """ So, I guess for Python 3 compatibility, I need to revert the change and return to PyString_..., as os.path.join returns str. Cheers, Simon -- 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] problem with 8.7.beta1
Hello compiling from source for SageMath version 8.7.beta1 on my opensuse leap 15.0 caused an error after compiling libffi. It looks like the problem mentioned at the bottom of #25900. It started as [libffi-3.2.1] [libffi-3.2.1] No record that 'libffi' was ever installed; skipping uninstall [libffi-3.2.1] Configuring libffi-3.2.1 [libffi-3.2.1] configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu ... and then ended with ... [libffi-3.2.1] /usr/bin/install -c -m 644 libffi.pc '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/inst/usr/local/sage/local/lib/pkgconfig' [libffi-3.2.1] make[7]: Leaving directory '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/src/x86_64-unknown-linux-gnu' [libffi-3.2.1] make[6]: Leaving directory '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/src/x86_64-unknown-linux-gnu' [libffi-3.2.1] make[5]: Leaving directory '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/src/x86_64-unknown-linux-gnu' [libffi-3.2.1] make[4]: Leaving directory '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/src' [libffi-3.2.1] [libffi-3.2.1] real 0m7.001s [libffi-3.2.1] user 0m5.834s [libffi-3.2.1] sys 0m1.524s [libffi-3.2.1] Copying package files from temporary location /usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/inst to /usr/local/sage/local [libffi-3.2.1] cp: cannot overwrite non-directory '/usr/local/sage/local/./lib64' with directory '/usr/local/sage/local/var/tmp/sage/build/libffi-3.2.1/inst/usr/local/sage/local/./lib64' /usr/local/sage/local/lib64 is an existing link to /usr/local/sage/local/lib/ full log attached. Chris -- 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. Found local metadata for libffi-3.2.1 Using cached file /usr/local/sage/upstream/libffi-3.2.1.tar.gz libffi-3.2.1 Setting up build directory for libffi-3.2.1 Finished extraction No patch files found in ../patches Host system: Linux linux-qk0i 4.12.14-lp150.12.45-default #1 SMP Mon Jan 14 20:29:59 UTC 2019 (7a62739) x86_64 x86_64 x86_64 GNU/Linux C compiler: gcc C compiler version: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-suse-linux/7/lto-wrapper OFFLOAD_TARGET_NAMES=hsa:nvptx-none Target: x86_64-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,ada,go --enable-offload-targets=hsa,nvptx-none=/usr/nvptx-none, --without-cuda-driver --enable-checking=release --disable-werror --with-gxx-include-dir=/usr/include/c++/7 --enable-ssp --disable-libssp --disable-libvtv --disable-libcc1 --disable-plugin --with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function --program-suffix=-7 --without-system-libunwind --enable-multilib --with-arch-32=x86-64 --with-tune=generic --build=x86_64-suse-linux --host=x86_64-suse-linux Thread model: posix gcc version 7.3.1 20180323 [gcc-7-branch revision 258812] (SUSE Linux) No record that 'libffi' was ever installed; skipping uninstall Configuring libffi-3.2.1 configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu continue configure in default builddir "./x86_64-unknown-linux-gnu" exec /bin/bash .././configure "--srcdir=.." "--enable-builddir=x86_64-unknown-linux-gnu" "linux gnu" configure: loading site script /usr/share/site/x86_64-unknown-linux-gnu checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for gsed... sed checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for gcc... gcc chec
[sage-devel] Re: python3 status report
Dear all, using "git worktree", I now have both python 2 and python 3 versions of Sage on my computer. Thank you! Of course, I started to check packages that I care about --- and immediately found a problem with the "meataxe" optional package. When trying to create a matrix of type Matrix_gfpn_dense, I get a TypeError: expected bytes, str found. Is there a ticket for meataxe on python 3 already? I guess not. So, unless someone stops me in the next hour or so, I'll open one... Best regards, Simon -- 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 status report
> Is there an apparent common reason for most of these failing tests? Such > as code that makes assumptions on sorting (which, IIRC, is different in > Python 2 and Python 3)? > Many many methods were relying on sorted list of vertices and edges. We have done significant progresses to reduce that. Another source of problems is that the order of keys of dictionary, i.e., list(mydict.keys()) or list(myset), might be different in py2 and py3. This breaks many doctests, but may be more complicated, it changes the order in which the neighbors of a vertex are visited (check G._backend.iterator_nbrs??). Consequently, the returned solution of some algorithms might be differents (but still correct). A solution is to tag doctests with py2 and py3. The most complicated issue is certainly edges of Graph: we sort the vertices of an edge before returning it... I have no solution for this issue. We can decide to stop ordering the vertices, but then we will have to update a very large number of algorithms. We could also design a method to compare object of different types. In fact, the main issue is that we use and compare vertices by id instead of mapping vertices to integer and work only with these integers. That would ease our life, but it's not easy to change that. David. -- 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: one patchbot misconfigured
So this patchbot belongs to nobody ? Too bad. It will then go on forever
spitting polluting reports (not useless reports nevertheless).
Recall to patchbot breeders: you can either use --owner=DiCarpaccio on the
command line or {'owner':'ClintWestwood'} in the patchbot config file to
tell us who you are. This is *useful*, ok ?
To patchbot breeders, please also check that you are running the latest
patchbot (2.8.2.dev0)
Frederic
Le mardi 8 janvier 2019 12:14:24 UTC+1, Frédéric Chapoton a écrit :
>
> Who is the owner of the patchbot nicknamed
>
> Ubuntu/18.04/x86_64/3.13.0-123-generic/44e979ad077a
>
> ?
>
> Please install *pyflakes* on your system, so that the patchbot runs
> correctly. This must be installed in the python version used to run the
> patchbot (and I suggest to use python3 for that).
>
> Frédéric
>
--
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: Sage python3 doctests
random example, containing both #py2 and #py3 tags Le dimanche 27 janvier 2019 19:24:08 UTC+1, John Cremona a écrit : > > > > On Sun, 27 Jan 2019 at 17:10, Frédéric Chapoton > wrote: > >> ok, then --optional=sage,py3 is ok (all doctests pass) whereas >> >> ./sage -t --optional=sage,py2 src/sage/modular/cusps_nf.py >> > > Is there a particular reason for this file being used as an example here? > I only say this as it was written by a student of mine and I may be one of > the few subscribers to this list who has much idea of what it does. > > > >> >> runs the py2 doctest and fail as expected >> >> same thing for >> >> ./sage -t --optional=sage,py2,py3 src/sage/modular/cusps_nf.py >> >> Le dimanche 27 janvier 2019 18:06:19 UTC+1, vdelecroix a écrit : >>> >>> This should be >>> >>> $ ./sage -t --optional=sage,py3 src/sage/modular/cusps_nf.py >>> >>> ie don't forget "sage". Otherwise the doctest without # are >>> not run. >>> >>> Le 27/01/2019 à 18:03, Frédéric Chapoton a écrit : >>> > This clearly needs a cleanup. For example, >>> > >>> > ./sage -t --optional=py2 src/sage/modular/cusps_nf.py >>> > >>> > ./sage -t --optional=py3 src/sage/modular/cusps_nf.py >>> > >>> > have unexpected effects (when tested using python3) >>> > >>> > >>> > >>> > Le dimanche 27 janvier 2019 17:54:54 UTC+1, Frédéric Chapoton a écrit >>> : >>> >> >>> >> Good question. Needs to be checked >>> >> >>> >> Le dimanche 27 janvier 2019 17:47:17 UTC+1, vdelecroix a écrit : >>> >>> >>> >>> What about doctests marked # python2 / # python3? >>> >>> >>> >>> Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit : >>> Strange, but still this runs the correct python >>> >>> ./sage -t --long src/sage/categories/finite_posets.py # 15 >>> doctests >>> >>> failed >>> >>> F >>> >>> Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : >>> > >>> > Hello, >>> > >>> > I wanted to run some doctests with my Python 3 Sage installation. >>> > However, running "sage -t" results in >>> > >>> > Using --optional=dochtml,memlimit,mpir,python2,sage >>> > >>> > ie, python2 is in the list. Is that expected? How should I >>> > run the tests? >>> > >>> > Vincent >>> > >>> >>> >>> >>> >> >>> > >>> >> -- >> 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] Re: Sage python3 doctests
On 2019-01-27 19:23, John Cremona wrote: On Sun, 27 Jan 2019 at 17:10, Frédéric Chapoton mailto:fchapot...@gmail.com>> wrote: ok, then --optional=sage,py3 is ok (all doctests pass) whereas ./sage -t --optional=sage,py2 src/sage/modular/cusps_nf.py Is there a particular reason for this file being used as an example here? I wasn't the original poster, but I think not. It's just a random example. -- 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: Sage python3 doctests
On Sun, 27 Jan 2019 at 17:10, Frédéric Chapoton wrote: > ok, then --optional=sage,py3 is ok (all doctests pass) whereas > > ./sage -t --optional=sage,py2 src/sage/modular/cusps_nf.py > Is there a particular reason for this file being used as an example here? I only say this as it was written by a student of mine and I may be one of the few subscribers to this list who has much idea of what it does. > > runs the py2 doctest and fail as expected > > same thing for > > ./sage -t --optional=sage,py2,py3 src/sage/modular/cusps_nf.py > > Le dimanche 27 janvier 2019 18:06:19 UTC+1, vdelecroix a écrit : >> >> This should be >> >> $ ./sage -t --optional=sage,py3 src/sage/modular/cusps_nf.py >> >> ie don't forget "sage". Otherwise the doctest without # are >> not run. >> >> Le 27/01/2019 à 18:03, Frédéric Chapoton a écrit : >> > This clearly needs a cleanup. For example, >> > >> > ./sage -t --optional=py2 src/sage/modular/cusps_nf.py >> > >> > ./sage -t --optional=py3 src/sage/modular/cusps_nf.py >> > >> > have unexpected effects (when tested using python3) >> > >> > >> > >> > Le dimanche 27 janvier 2019 17:54:54 UTC+1, Frédéric Chapoton a écrit : >> >> >> >> Good question. Needs to be checked >> >> >> >> Le dimanche 27 janvier 2019 17:47:17 UTC+1, vdelecroix a écrit : >> >>> >> >>> What about doctests marked # python2 / # python3? >> >>> >> >>> Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit : >> Strange, but still this runs the correct python >> >> ./sage -t --long src/sage/categories/finite_posets.py # 15 doctests >> >>> failed >> >> F >> >> Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : >> > >> > Hello, >> > >> > I wanted to run some doctests with my Python 3 Sage installation. >> > However, running "sage -t" results in >> > >> > Using --optional=dochtml,memlimit,mpir,python2,sage >> > >> > ie, python2 is in the list. Is that expected? How should I >> > run the tests? >> > >> > Vincent >> > >> >> >>> >> >> >> > >> > -- > 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.
Re: [sage-devel] Re: Sage python3 doctests
Le 27/01/2019 à 18:12, Vincent Delecroix a écrit : PS: without a decent "sage -t" I would not advice any developer to switch to Python3 Sage... https://trac.sagemath.org/ticket/27150 -- 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: Sage python3 doctests
But I don't understand - why the py2 / py3 flag is not set correctly in --optional (it should have been set by sage/doctest/control.py) - what is this python2 appearing in --optional? where it is set? Vincent PS: without a decent "sage -t" I would not advice any developer to switch to Python3 Sage... Le 27/01/2019 à 18:10, Frédéric Chapoton a écrit : ok, then --optional=sage,py3 is ok (all doctests pass) whereas ./sage -t --optional=sage,py2 src/sage/modular/cusps_nf.py runs the py2 doctest and fail as expected same thing for ./sage -t --optional=sage,py2,py3 src/sage/modular/cusps_nf.py Le dimanche 27 janvier 2019 18:06:19 UTC+1, vdelecroix a écrit : This should be $ ./sage -t --optional=sage,py3 src/sage/modular/cusps_nf.py ie don't forget "sage". Otherwise the doctest without # are not run. Le 27/01/2019 à 18:03, Frédéric Chapoton a écrit : This clearly needs a cleanup. For example, ./sage -t --optional=py2 src/sage/modular/cusps_nf.py ./sage -t --optional=py3 src/sage/modular/cusps_nf.py have unexpected effects (when tested using python3) Le dimanche 27 janvier 2019 17:54:54 UTC+1, Frédéric Chapoton a écrit : Good question. Needs to be checked Le dimanche 27 janvier 2019 17:47:17 UTC+1, vdelecroix a écrit : What about doctests marked # python2 / # python3? Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit : Strange, but still this runs the correct python ./sage -t --long src/sage/categories/finite_posets.py # 15 doctests failed F Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : Hello, I wanted to run some doctests with my Python 3 Sage installation. However, running "sage -t" results in Using --optional=dochtml,memlimit,mpir,python2,sage ie, python2 is in the list. Is that expected? How should I run the tests? Vincent -- 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: Sage python3 doctests
ok, then --optional=sage,py3 is ok (all doctests pass) whereas ./sage -t --optional=sage,py2 src/sage/modular/cusps_nf.py runs the py2 doctest and fail as expected same thing for ./sage -t --optional=sage,py2,py3 src/sage/modular/cusps_nf.py Le dimanche 27 janvier 2019 18:06:19 UTC+1, vdelecroix a écrit : > > This should be > > $ ./sage -t --optional=sage,py3 src/sage/modular/cusps_nf.py > > ie don't forget "sage". Otherwise the doctest without # are > not run. > > Le 27/01/2019 à 18:03, Frédéric Chapoton a écrit : > > This clearly needs a cleanup. For example, > > > > ./sage -t --optional=py2 src/sage/modular/cusps_nf.py > > > > ./sage -t --optional=py3 src/sage/modular/cusps_nf.py > > > > have unexpected effects (when tested using python3) > > > > > > > > Le dimanche 27 janvier 2019 17:54:54 UTC+1, Frédéric Chapoton a écrit : > >> > >> Good question. Needs to be checked > >> > >> Le dimanche 27 janvier 2019 17:47:17 UTC+1, vdelecroix a écrit : > >>> > >>> What about doctests marked # python2 / # python3? > >>> > >>> Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit : > Strange, but still this runs the correct python > > ./sage -t --long src/sage/categories/finite_posets.py # 15 doctests > >>> failed > > F > > Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : > > > > Hello, > > > > I wanted to run some doctests with my Python 3 Sage installation. > > However, running "sage -t" results in > > > > Using --optional=dochtml,memlimit,mpir,python2,sage > > > > ie, python2 is in the list. Is that expected? How should I > > run the tests? > > > > Vincent > > > > >>> > >> > > > -- 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: Sage python3 doctests
This should be $ ./sage -t --optional=sage,py3 src/sage/modular/cusps_nf.py ie don't forget "sage". Otherwise the doctest without # are not run. Le 27/01/2019 à 18:03, Frédéric Chapoton a écrit : This clearly needs a cleanup. For example, ./sage -t --optional=py2 src/sage/modular/cusps_nf.py ./sage -t --optional=py3 src/sage/modular/cusps_nf.py have unexpected effects (when tested using python3) Le dimanche 27 janvier 2019 17:54:54 UTC+1, Frédéric Chapoton a écrit : Good question. Needs to be checked Le dimanche 27 janvier 2019 17:47:17 UTC+1, vdelecroix a écrit : What about doctests marked # python2 / # python3? Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit : Strange, but still this runs the correct python ./sage -t --long src/sage/categories/finite_posets.py # 15 doctests failed F Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : Hello, I wanted to run some doctests with my Python 3 Sage installation. However, running "sage -t" results in Using --optional=dochtml,memlimit,mpir,python2,sage ie, python2 is in the list. Is that expected? How should I run the tests? Vincent -- 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: Sage python3 doctests
This clearly needs a cleanup. For example, ./sage -t --optional=py2 src/sage/modular/cusps_nf.py ./sage -t --optional=py3 src/sage/modular/cusps_nf.py have unexpected effects (when tested using python3) Le dimanche 27 janvier 2019 17:54:54 UTC+1, Frédéric Chapoton a écrit : > > Good question. Needs to be checked > > Le dimanche 27 janvier 2019 17:47:17 UTC+1, vdelecroix a écrit : >> >> What about doctests marked # python2 / # python3? >> >> Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit : >> > Strange, but still this runs the correct python >> > >> > ./sage -t --long src/sage/categories/finite_posets.py # 15 doctests >> failed >> > >> > F >> > >> > Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : >> >> >> >> Hello, >> >> >> >> I wanted to run some doctests with my Python 3 Sage installation. >> >> However, running "sage -t" results in >> >> >> >> Using --optional=dochtml,memlimit,mpir,python2,sage >> >> >> >> ie, python2 is in the list. Is that expected? How should I >> >> run the tests? >> >> >> >> Vincent >> >> >> > >> > -- 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: Sage python3 doctests
Good question. Needs to be checked Le dimanche 27 janvier 2019 17:47:17 UTC+1, vdelecroix a écrit : > > What about doctests marked # python2 / # python3? > > Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit : > > Strange, but still this runs the correct python > > > > ./sage -t --long src/sage/categories/finite_posets.py # 15 doctests > failed > > > > F > > > > Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : > >> > >> Hello, > >> > >> I wanted to run some doctests with my Python 3 Sage installation. > >> However, running "sage -t" results in > >> > >> Using --optional=dochtml,memlimit,mpir,python2,sage > >> > >> ie, python2 is in the list. Is that expected? How should I > >> run the tests? > >> > >> Vincent > >> > > > -- 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: Sage python3 doctests
What about doctests marked # python2 / # python3? Le 27/01/2019 à 17:46, Frédéric Chapoton a écrit : Strange, but still this runs the correct python ./sage -t --long src/sage/categories/finite_posets.py # 15 doctests failed F Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : Hello, I wanted to run some doctests with my Python 3 Sage installation. However, running "sage -t" results in Using --optional=dochtml,memlimit,mpir,python2,sage ie, python2 is in the list. Is that expected? How should I run the tests? Vincent -- 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: Sage python3 doctests
Strange, but still this runs the correct python ./sage -t --long src/sage/categories/finite_posets.py # 15 doctests failed F Le dimanche 27 janvier 2019 17:35:41 UTC+1, vdelecroix a écrit : > > Hello, > > I wanted to run some doctests with my Python 3 Sage installation. > However, running "sage -t" results in > > Using --optional=dochtml,memlimit,mpir,python2,sage > > ie, python2 is in the list. Is that expected? How should I > run the tests? > > Vincent > -- 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] Sage python3 doctests
Hello, I wanted to run some doctests with my Python 3 Sage installation. However, running "sage -t" results in Using --optional=dochtml,memlimit,mpir,python2,sage ie, python2 is in the list. Is that expected? How should I run the tests? Vincent -- 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 status report
Hi Frédéric, On 2019-01-27, Frédéric Chapoton wrote: > Does this mean that everything dependent on python will have to be > recompiled when you switch ? My original worktree was ~/Sage/git/sage. I added a new worktree ~/Sage/git/py3 using "git worktree add". The fact that ~/Sage/git/sage/local and ~/Sage/git/py3/local are not the same probably means that no recompilation will be needed. Best regards, Simon -- 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 status report
Does this mean that everything dependent on python will have to be recompiled when you switch ? F Le dimanche 27 janvier 2019 16:26:17 UTC+1, Timo Kaufmann a écrit : > > > > Am Sonntag, 27. Januar 2019 14:32:16 UTC+1 schrieb Simon King: > >> > *STATEMENT *: I would to advocate that **every developer switch to >> python3 >> > NOW**. >> >> How? >> > > Git worktrees would be a solution. Essentially you keep one git > repository, but check out two branches at the same time in different > directories. From your main repo do this: > > $ git worktree add /path/to/the/new/checkout branch-to-checkout > > You'll keep your python2 checkout and the new directory will be part of > the same repo. That means that remotes are set up as before and you have > access to the same branches. You can also create a new branch and > immediately create a worktree for that: > > $ git worktree add -b my-feature-branch /path/to/the/new/checkout > branch-to-checkout > > > -- 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 status report
Hi Timo, On 2019-01-27, Timo Kaufmann wrote: > Git worktrees would be a solution. Essentially you keep one git repository, > but check out two branches at the same time in different directories. From > your main repo do this: > > $ git worktree add /path/to/the/new/checkout branch-to-checkout Thank you! I am trying this, also having a symlink to the original worktree's "upstream" directory. Best regards, Simon -- 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 status report
Am Sonntag, 27. Januar 2019 14:32:16 UTC+1 schrieb Simon King: > > *STATEMENT *: I would to advocate that **every developer switch to > python3 > > NOW**. > > How? > Git worktrees would be a solution. Essentially you keep one git repository, but check out two branches at the same time in different directories. From your main repo do this: $ git worktree add /path/to/the/new/checkout branch-to-checkout You'll keep your python2 checkout and the new directory will be part of the same repo. That means that remotes are set up as before and you have access to the same branches. You can also create a new branch and immediately create a worktree for that: $ git worktree add -b my-feature-branch /path/to/the/new/checkout branch-to-checkout -- 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: python3 status report
Le 27/01/2019 à 15:56, Simon King a écrit : Hi Vincent, On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: king@klap:~/Sage/py3/sage$ git remote add trac g...@trac.sagemath.org:sage.git After that, you should see "trac" among your remotes $ git remote -v And "origin" should be your local repo. Correct! king@klap:~/Sage/py3/sage$ git remote -v origin /home/king/Sage/py3/../git/sage (fetch) origin /home/king/Sage/py3/../git/sage (push) tracg...@trac.sagemath.org:sage.git (fetch) trac g...@trac.sagemath.org:sage.git (push) $ git branch --set-upstream-to trac/develop king@klap:~/Sage/py3/sage$ git branch * develop t/13447/make_libsingular_multivariate_polynomial_rings_collectable So, indeed we are talking about "develop", but: king@klap:~/Sage/py3/sage$ git branch --set-upstream-to trac/develop error: the requested upstream branch 'trac/develop' does not exist hint: hint: If you are planning on basing your work on an upstream hint: branch that already exists at the remote, you may need to hint: run "git fetch" to retrieve it. hint: hint: If you are planning to push out a new local branch that hint: will track its remote counterpart, you may want to use hint: "git push -u" to set the upstream config as you push. git has no clue what is on trac (of course) but apparently does not want to find out automatically. Do $ git fetch trac develop so that it knows. And then $ git branch --set-upstream-to trac/develop (I tried and it worked). Though "git pull" is not a so good idea since that would pull *all* branches from trac. You would better run $ git pull trac develop Vincent -- 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] python3 status report
It is blocking https://trac.sagemath.org/ticket/26792 Le dimanche 27 janvier 2019 15:56:02 UTC+1, Jeroen Demeyer a écrit : > > On 2019-01-27 14:23, Frédéric Chapoton wrote: > > Some good python3 changes are blocked by the long awaited ticket > > https://trac.sagemath.org/ticket/23572 > > What do you mean with that? It's a ticket adding doctests for a book, > how is that related to Python 3 porting? > -- 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 status report
Hi Vincent, On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: >> king@klap:~/Sage/py3/sage$ git remote add trac >> g...@trac.sagemath.org:sage.git > > After that, you should see "trac" among your remotes > > $ git remote -v > > And "origin" should be your local repo. Correct! king@klap:~/Sage/py3/sage$ git remote -v origin /home/king/Sage/py3/../git/sage (fetch) origin /home/king/Sage/py3/../git/sage (push) tracg...@trac.sagemath.org:sage.git (fetch) tracg...@trac.sagemath.org:sage.git (push) >$ git branch --set-upstream-to trac/develop king@klap:~/Sage/py3/sage$ git branch * develop t/13447/make_libsingular_multivariate_polynomial_rings_collectable So, indeed we are talking about "develop", but: king@klap:~/Sage/py3/sage$ git branch --set-upstream-to trac/develop error: the requested upstream branch 'trac/develop' does not exist hint: hint: If you are planning on basing your work on an upstream hint: branch that already exists at the remote, you may need to hint: run "git fetch" to retrieve it. hint: hint: If you are planning to push out a new local branch that hint: will track its remote counterpart, you may want to use hint: "git push -u" to set the upstream config as you push. So, still something is wrong. Best regards, Simon -- 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] python3 status report
On 2019-01-27 14:23, Frédéric Chapoton wrote: Some good python3 changes are blocked by the long awaited ticket https://trac.sagemath.org/ticket/23572 What do you mean with that? It's a ticket adding doctests for a book, how is that related to Python 3 porting? -- 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: python3 status report
Hi Simon, Le 27/01/2019 à 15:19, Simon King a écrit : On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: This has nothing to do with python 3. Sure. You only need to set up properly your remote and branches. Exactly. And that's already more than what I can do in git without reading tons of documentation. After $ git clone sage-original sage-py3 The default remote in sage-py3 will be the sage-original local folder. First step, add the remote for trac (sage-py3) $ git remote add trac g...@trac.sagemath.org:sage.git Second step set trac to be the default upstream (sage-py3) $ git branch --set-upstream-to trac Doesn't work for me. My bad. king@klap:~/Sage/py3/sage$ git remote add trac g...@trac.sagemath.org:sage.git After that, you should see "trac" among your remotes $ git remote -v And "origin" should be your local repo. king@klap:~/Sage/py3/sage$ git branch --set-upstream-to trac This was an erroneous command. It is $ git branch --set-upstream-to trac/develop (or trac/mater if you cloned the master branch) Note that this will only take care of the current branch (develop). Vincent -- 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: python3 status report
I believe it was added by What I am unsure about now (too hard to dig using a phone :-)) is how to switch between different SAGE_LOCAL. Probably by setting an env. variable. https://trac.sagemath.org/ticket/21479 On Sun, 27 Jan 2019 14:12 Vincent Delecroix <20100.delecr...@gmail.com wrote: > Please tell us how. None of us claimed that two clones were needed. > > Le 27/01/2019 à 15:03, Dima Pasechnik a écrit : > > Why does one need two clones? We have functionality to allow a custom > build > > location. It should be possible to give it to configure as a parameter... > > > > On Sun, 27 Jan 2019 13:58 Vincent Delecroix <20100.delecr...@gmail.com > > wrote: > > > >> > >> > >> Le 27/01/2019 à 14:50, Simon King a écrit : > >>> Hi Vincent, > >>> > >>> On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > You need a different clone of your git repo, let say sage-py3. > >>> > >>> How to do so most easily, so that "git pull" etc. still referes to > trac? > >>> That was part of my question. Doing "git pull > >>> /path/to/my/old/installation" would mean that I need to go to my old > >>> installation, "git pull" (pulls develop from trac), go to the new > >>> installation, and to "git pull" again (pulling develop from my old > >>> installation, but NOT directly from trac). > >> > >> This has nothing to do with python 3. You only need to set up > >> properly your remote and branches. > >> > >> After > >> > >> $ git clone sage-original sage-py3 > >> > >> The default remote in sage-py3 will be the sage-original local > >> folder. First step, add the remote for trac > >> > >>(sage-py3) $ git remote add trac g...@trac.sagemath.org:sage.git > >> > >> Second step set trac to be the default upstream > >> > >>(sage-py3) $ git branch --set-upstream-to trac > >> > >> For all this, the best is to read the git documentation. > >> > >> Vincent > >> > >> PS: the Frederic version is less trouble but more bandwidth! > >> > >> -- > >> 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.
[sage-devel] Re: python3 status report
Hi Vincent, On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > This has nothing to do with python 3. Sure. > You only need to set up > properly your remote and branches. Exactly. And that's already more than what I can do in git without reading tons of documentation. > After > >$ git clone sage-original sage-py3 > > The default remote in sage-py3 will be the sage-original local > folder. First step, add the remote for trac > > (sage-py3) $ git remote add trac g...@trac.sagemath.org:sage.git > > Second step set trac to be the default upstream > > (sage-py3) $ git branch --set-upstream-to trac Doesn't work for me. king@klap:~/Sage/py3/sage$ git remote add trac g...@trac.sagemath.org:sage.git king@klap:~/Sage/py3/sage$ git branch --set-upstream-to trac error: the requested upstream branch 'trac' does not exist hint: hint: If you are planning on basing your work on an upstream hint: branch that already exists at the remote, you may need to hint: run "git fetch" to retrieve it. hint: hint: If you are planning to push out a new local branch that hint: will track its remote counterpart, you may want to use hint: "git push -u" to set the upstream config as you push. > PS: the Frederic version is less trouble but more bandwidth! Exactly. I thought a local copy would be both faster and easier to obtain. Best regards, Simon -- 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: python3 status report
Please tell us how. None of us claimed that two clones were needed. Le 27/01/2019 à 15:03, Dima Pasechnik a écrit : Why does one need two clones? We have functionality to allow a custom build location. It should be possible to give it to configure as a parameter... On Sun, 27 Jan 2019 13:58 Vincent Delecroix <20100.delecr...@gmail.com wrote: Le 27/01/2019 à 14:50, Simon King a écrit : Hi Vincent, On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: You need a different clone of your git repo, let say sage-py3. How to do so most easily, so that "git pull" etc. still referes to trac? That was part of my question. Doing "git pull /path/to/my/old/installation" would mean that I need to go to my old installation, "git pull" (pulls develop from trac), go to the new installation, and to "git pull" again (pulling develop from my old installation, but NOT directly from trac). This has nothing to do with python 3. You only need to set up properly your remote and branches. After $ git clone sage-original sage-py3 The default remote in sage-py3 will be the sage-original local folder. First step, add the remote for trac (sage-py3) $ git remote add trac g...@trac.sagemath.org:sage.git Second step set trac to be the default upstream (sage-py3) $ git branch --set-upstream-to trac For all this, the best is to read the git documentation. Vincent PS: the Frederic version is less trouble but more bandwidth! -- 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.
Re: [sage-devel] Re: python3 status report
Why does one need two clones? We have functionality to allow a custom build location. It should be possible to give it to configure as a parameter... On Sun, 27 Jan 2019 13:58 Vincent Delecroix <20100.delecr...@gmail.com wrote: > > > Le 27/01/2019 à 14:50, Simon King a écrit : > > Hi Vincent, > > > > On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > >> You need a different clone of your git repo, let say sage-py3. > > > > How to do so most easily, so that "git pull" etc. still referes to trac? > > That was part of my question. Doing "git pull > > /path/to/my/old/installation" would mean that I need to go to my old > > installation, "git pull" (pulls develop from trac), go to the new > > installation, and to "git pull" again (pulling develop from my old > > installation, but NOT directly from trac). > > This has nothing to do with python 3. You only need to set up > properly your remote and branches. > > After > >$ git clone sage-original sage-py3 > > The default remote in sage-py3 will be the sage-original local > folder. First step, add the remote for trac > > (sage-py3) $ git remote add trac g...@trac.sagemath.org:sage.git > > Second step set trac to be the default upstream > > (sage-py3) $ git branch --set-upstream-to trac > > For all this, the best is to read the git documentation. > > Vincent > > PS: the Frederic version is less trouble but more bandwidth! > > -- > 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.
Re: [sage-devel] Re: python3 status report
PPS: if you intend to have a py2 and py3 installation it is a good idea to have a shared $SAGE_ROOT/upstream/ repository (where package tarballs are downloaded). This can be done via a simple simlink in the py3 installation. Maybe we could create a configure option --with-upstream=PATH for this? Vincent Le 27/01/2019 à 14:56, Frédéric Chapoton a écrit : git clone git://github.com/sagemath/sage.git sage3 Le dimanche 27 janvier 2019 14:50:22 UTC+1, Simon King a écrit : Hi Vincent, On 2019-01-27, Vincent Delecroix <20100.d...@gmail.com > wrote: You need a different clone of your git repo, let say sage-py3. How to do so most easily, so that "git pull" etc. still referes to trac? That was part of my question. Doing "git pull /path/to/my/old/installation" would mean that I need to go to my old installation, "git pull" (pulls develop from trac), go to the new installation, and to "git pull" again (pulling develop from my old installation, but NOT directly from trac). That's awkward and could certainly be done better. In that clone, do $ make configure $ ./configure --with-python=3 Thank you! Best regards, Simon -- 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: python3 status report
Le 27/01/2019 à 14:50, Simon King a écrit : Hi Vincent, On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: You need a different clone of your git repo, let say sage-py3. How to do so most easily, so that "git pull" etc. still referes to trac? That was part of my question. Doing "git pull /path/to/my/old/installation" would mean that I need to go to my old installation, "git pull" (pulls develop from trac), go to the new installation, and to "git pull" again (pulling develop from my old installation, but NOT directly from trac). This has nothing to do with python 3. You only need to set up properly your remote and branches. After $ git clone sage-original sage-py3 The default remote in sage-py3 will be the sage-original local folder. First step, add the remote for trac (sage-py3) $ git remote add trac g...@trac.sagemath.org:sage.git Second step set trac to be the default upstream (sage-py3) $ git branch --set-upstream-to trac For all this, the best is to read the git documentation. Vincent PS: the Frederic version is less trouble but more bandwidth! -- 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 status report
git clone git://github.com/sagemath/sage.git sage3 Le dimanche 27 janvier 2019 14:50:22 UTC+1, Simon King a écrit : > > Hi Vincent, > > On 2019-01-27, Vincent Delecroix <20100.d...@gmail.com > > wrote: > > You need a different clone of your git repo, let say sage-py3. > > How to do so most easily, so that "git pull" etc. still referes to trac? > That was part of my question. Doing "git pull > /path/to/my/old/installation" would mean that I need to go to my old > installation, "git pull" (pulls develop from trac), go to the new > installation, and to "git pull" again (pulling develop from my old > installation, but NOT directly from trac). > > That's awkward and could certainly be done better. > > >In that > > clone, do > > > > $ make configure > > $ ./configure --with-python=3 > > Thank you! > > Best regards, > Simon > > -- 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 status report
Hi Frédéric, On 2019-01-27, Frédéric Chapoton wrote: > I am pretty sure you would be rather happy working only with python3. That's too early. For teaching, I need to know that I have a working Sage installation, and for research I also have to have a working installation of my group cohomology spkg. So far, there is no way for me to be sure that python3 would work for me. Also, there is a high probability that I need to refactor my group cohomology spkg so that it works in python3. So, FOR NOW, I won't immediately drop python2. Best regards, Simon -- 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 status report
Hi Vincent, On 2019-01-27, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > You need a different clone of your git repo, let say sage-py3. How to do so most easily, so that "git pull" etc. still referes to trac? That was part of my question. Doing "git pull /path/to/my/old/installation" would mean that I need to go to my old installation, "git pull" (pulls develop from trac), go to the new installation, and to "git pull" again (pulling develop from my old installation, but NOT directly from trac). That's awkward and could certainly be done better. >In that > clone, do > > $ make configure > $ ./configure --with-python=3 Thank you! Best regards, Simon -- 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 status report
> > > > *STATEMENT *: I would to advocate that **every developer switch to > python3 > > NOW**. > > How? > > To make my question more precise: For production I would like to > keep a python 2 installation of Sage. I am pretty sure you would be rather happy working only with python3. > So, given my existing Sage > installation, what would be the easiest way to create a second > installation with python 3 that is automatically configured to work > well with "git trac"? I guess it is some kind of git clone. Also I > don't know what make target is needed. > > How to build sage with python3: first "git clone" into another dir, say "sage3" then inside this dir: make configure ./configure --with-python=3 make build The first two lines need only be used once and for all. concerning the tests, there is currently a partial test target that ensure that thing know to pass still pass if you want to run all tests, then all course, you will meet failures in some parts of sage -- 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: python3 status report
Le 27/01/2019 à 14:32, Simon King a écrit : Hi Frédéric, On 2019-01-27, Frédéric Chapoton wrote: (2) the most badly failing file is "explain_pickle" with 70 failing doctests. Hopefully, this will be treated very carefully by Erik M. Bray (3) after that, we still have problems with graph, where generic_graph.py has 50 failing doctests. But good progress was made by David Coudert, Is there an apparent common reason for most of these failing tests? Such as code that makes assumptions on sorting (which, IIRC, is different in Python 2 and Python 3)? *STATEMENT *: I would to advocate that **every developer switch to python3 NOW**. How? To make my question more precise: For production I would like to keep a python 2 installation of Sage. So, given my existing Sage installation, what would be the easiest way to create a second installation with python 3 that is automatically configured to work well with "git trac"? I guess it is some kind of git clone. Also I don't know what make target is needed. You need a different clone of your git repo, let say sage-py3. In that clone, do $ make configure $ ./configure --with-python=3 Then, unless you rerun configure, every call to make will take care of the Python 3 switch automatically. See also https://wiki.sagemath.org/Python3-compatible%20code Vincent -- 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 status report
Hi Frédéric, On 2019-01-27, Frédéric Chapoton wrote: > (2) the most badly failing file is "explain_pickle" with 70 failing > doctests. Hopefully, this will be treated very carefully by Erik M. Bray > > (3) after that, we still have problems with graph, where generic_graph.py > has 50 failing doctests. But good progress was made by David Coudert, Is there an apparent common reason for most of these failing tests? Such as code that makes assumptions on sorting (which, IIRC, is different in Python 2 and Python 3)? > *STATEMENT *: I would to advocate that **every developer switch to python3 > NOW**. How? To make my question more precise: For production I would like to keep a python 2 installation of Sage. So, given my existing Sage installation, what would be the easiest way to create a second installation with python 3 that is automatically configured to work well with "git trac"? I guess it is some kind of git clone. Also I don't know what make target is needed. Best regards, Simon -- 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 status report
Hello everybody, here is a small progress report on porting sage to python3. Good, but still too slow for my taste. The sooner we can catch up with jupyter, the better.. (1) with the latest beta (8.7.b1), there are now exactly 200 files having failing doctests, and a total of 866 failing doctests. Among those, 74 files have 1 failing doctest. (2) the most badly failing file is "explain_pickle" with 70 failing doctests. Hopefully, this will be treated very carefully by Erik M. Bray (3) after that, we still have problems with graph, where generic_graph.py has 50 failing doctests. But good progress was made by David Coudert, (4) then, various small issues, such as sorting sets and dictionaries, etc. Some good python3 changes are blocked by the long awaited ticket https://trac.sagemath.org/ticket/23572 *STATEMENT *: I would to advocate that **every developer switch to python3 NOW**. This will help to prevent regressions, as the one that happened recently in elliptic curves. This will also motivate people to fix the part of the code base that they use and that still fails. Please vote ! Frédéric -- 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.
