[sage-release] Re: Sage 8.9.beta8 released

On Sunday, August 25, 2019 at 3:37:50 PM UTC-7, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at > http://www.sagemath.org/download-latest.html > > It is nearing the end of the 8.9

Re: [sage-release] Re: Sage 8.7.beta6 released

Yes, that fits. Now that I know to look, I see buried in my gap install log Uninstalling existing 'gap' Running pre-uninstall script for 'gap' /Users/jpalmier/Desktop/Sage/git/sage/local/var/lib/sage/scripts/gap/spkg-prerm: line 13:

[sage-support] debian virtual machine numerical noise

In order to try to track down the problem with Python 3 and polynomial_rational_flint.pyx on Debian (see https://trac.sagemath.org/ticket/28334 — help wanted!), I installed VirtualBox and a Debian 10 virtual machine on my iMac. Most doctests pass, but I am getting some numerical noise. Did I

Re: [sage-release] Re: Sage 8.9.beta4 released

On Tuesday, August 6, 2019 at 5:55:53 AM UTC-7, E. Madison Bray wrote: > > On Tue, Aug 6, 2019 at 2:45 PM Eric Gourgoulhon > wrote: > > > > Le vendredi 2 août 2019 18:07:16 UTC+2, John H Palmieri a écrit : > >> > >> > >> > >> On Fri

[sage-release] Re: Sage 8.9.beta5 released

New failure with Python 3: sage -t --warn-long 78.7 src/sage/tests/cmdline.py ** File "src/sage/tests/cmdline.py", line 503, in sage.tests.cmdline.test_executable Failed example: print(err) Expected: Cython

[sage-devel] Re: Grepping Trac

On Friday, August 2, 2019 at 1:36:36 PM UTC-7, Nils Bruin wrote: > > On Friday, August 2, 2019 at 11:39:47 AM UTC-7, Timo Kaufmann wrote: >> >> Hi! >> >> As part of my packaging workflow, I find myself pasting error messages >> into the trac search pretty frequently to discover if something is

[sage-release] Re: Sage 8.9.beta4 released

On Friday, August 2, 2019 at 9:07:16 AM UTC-7, John H Palmieri wrote: > > > > On Friday, August 2, 2019 at 3:31:07 AM UTC-7, Eric Gourgoulhon wrote: >> >> >> >> Le vendredi 2 août 2019 01:00:29 UTC+2, John H Palmieri a écrit : >>> >>

[sage-release] Re: Sage 8.9.beta4 released

On Friday, August 2, 2019 at 3:31:07 AM UTC-7, Eric Gourgoulhon wrote: > > > > Le vendredi 2 août 2019 01:00:29 UTC+2, John H Palmieri a écrit : >> >> Another question: does Flint pass its test suite on these machines? >> > > How could I run this test su

[sage-release] Re: Sage 8.9.beta4 released

Another question: does Flint pass its test suite on these machines? On Thursday, August 1, 2019 at 3:52:07 PM UTC-7, John H Palmieri wrote: > > Do you get the same failure with Python 2? If not, any ideas why > "Exception (FLINT memory_manager). Unable to allocate memory

[sage-release] Re: Sage 8.9.beta4 released

Do you get the same failure with Python 2? If not, any ideas why "Exception (FLINT memory_manager). Unable to allocate memory" would depend on the version of Python? Flint doesn't depend on Python, so if it's Python 3 only, is there some issue with the Flint interface? On Tuesday, July 30,

Re: [sage-support] Is there a binary version of SageMath .app.dmg compatiable with Mac OS X ver. 10.14.6

On Friday, July 26, 2019 at 9:33:25 AM UTC-7, John H Palmieri wrote: > > > > On Friday, July 26, 2019 at 12:32:06 AM UTC-7, Dima Pasechnik wrote: >> >> >> >> On Fri, 26 Jul 2019 at 06:26, Samuel Dupree wrote: >> >>> >>> >>> I

Re: [sage-support] Is there a binary version of SageMath .app.dmg compatiable with Mac OS X ver. 10.14.6

On Friday, July 26, 2019 at 12:32:06 AM UTC-7, Dima Pasechnik wrote: > > > > On Fri, 26 Jul 2019 at 06:26, Samuel Dupree > wrote: > >> >> >> I'm attempting to update SageMath-8.7.app on an iMacPro running Mac OS X >> ver. 10.14.6 tp SageMath-8.8.app. The problem for the moment occurs when I

[sage-devel] signature missing in introspection some of the time

See https://ask.sagemath.org/question/47214/help-doesnt-show-function-call/. Some of the time when you evaluate blah? the signature is not present. Is this a bug or is it intended? I like this behavior: sage: A = SteenrodAlgebra() sage: A.antipode? Signature: B.antipode(self, *args)

Re: [sage-devel] sage foundation ???

I am writing to follow up on this. The University of Washington has now stopped accepting donations to the Sage Foundation fund. People looking for ways to donate in support of Sage will need to find other avenues for that, and I encourage people to create those avenues if they know how. Of

Re: [sage-support] The behavior of empty sums

On Tuesday, June 25, 2019 at 3:10:29 AM UTC-7, Peter Luschny wrote: > > Am Di., 25. Juni 2019 um 10:49 Uhr 'luisfe' : > > | When n =0, k ranges from 0 to -1 so there is no k and the list > constructed in ib(n,m) > | is just the empty list. Not an empty list of polynomials, just an empty >

Re: [sage-release] Re: Sage 8.8.rc2 released

This problem is being discussed at https://trac.sagemath.org/ticket/28008. As François says, you can touch matrix_rational_dense.pyx and do "sage -b", or you can do "sage -ba" to rebuild all of Sage's library files, in case other ones are also affected. On Wednesday, June 19, 2019 at 5:52:19

[sage-devel] Re: Installation gets stuck when it tries to download zeromq-4.2.5.tar.gz

On Tuesday, June 18, 2019 at 10:12:06 AM UTC-7, Parth Dubal wrote: > > I tried to download manually and put it into upstream directory but it is > already present and the installation didn't even reach to that step. I > don't understand, if it was already downloaded earlier then why the >

[sage-devel] Re: Installation gets stuck when it tries to download zeromq-4.2.5.tar.gz

On Tuesday, June 18, 2019 at 8:47:31 AM UTC-7, Parth Dubal wrote: > > Hi, > > I tried three times to install sage as described in github on my virtual > machine (Ubuntu 19) but the installation gets stuck for hours at the point > of downloading zeromq-4.2.5.tar.gz. I am running ubuntu on

[sage-release] Re: Sage 8.8.rc0 released

I am having a problem on a different OS X machine (an iMac Pro): sage -t src/doc/en/thematic_tutorials/explicit_methods_in_number_theory/birds_other.rst Bad exit: 1 ** ... sage: dimension(M.cuspidal_subspace()) ## line 109

Re: [sage-release] Sage 8.8.rc0 released

d for me, too. > > David. > > Le 9 juin 2019 à 23:23, John H Palmieri > > a écrit : > > I performed the incremental build the way I always do: "git pull trac" > followed by "make". When I ran into problems, I restarted from 8.8.beta7, > wh

Re: [sage-release] Sage 8.8.rc0 released

is an incremental build problem. > Something that should have been rebuilt didn’t and that may be because of > the way you performed the incremental build. > > François > > > On 10/06/2019, at 7:46 AM, John H Palmieri > wrote: > > > > > > > > O

Re: [sage-release] Sage 8.8.rc0 released

On Sunday, June 9, 2019 at 12:37:52 PM UTC-7, John H Palmieri wrote: > > I think the problem is with the openblas upgrade, > https://trac.sagemath.org/ticket/27847. > I opened https://trac.sagemath.org/ticket/27961 (not that I know how to fix it...) > > > On Sunday, Jun

Re: [sage-release] Sage 8.8.rc0 released

I think the problem is with the openblas upgrade, https://trac.sagemath.org/ticket/27847. On Sunday, June 9, 2019 at 10:19:27 AM UTC-7, David Coudert wrote: > > crash with both python 2 and python 3 on osX. I attach the crash report > with python 3. > > Any help is more than welcome. > >

Re: [sage-devel] Apple deprecates Python

On Saturday, June 8, 2019 at 8:56:09 AM UTC-7, Dima Pasechnik wrote: > > > > On Sat, 8 Jun 2019 16:50 John H Palmieri, > wrote: > >> >> >> On Saturday, June 8, 2019 at 1:25:11 AM UTC-7, vdelecroix wrote: >>> >>> Le 07/06/2019 à 16:44,

Re: [sage-devel] Apple deprecates Python

On Saturday, June 8, 2019 at 1:25:11 AM UTC-7, vdelecroix wrote: > > Le 07/06/2019 à 16:44, Jeroen Demeyer a écrit : > > On 2019-06-07 16:38, E. Madison Bray wrote: > >> While I agree it's part of an annoying trend, this is one change I > >> welcome: The Python interpreter shipped in OSX has

Re: [sage-devel] Apple deprecates Python

On Friday, June 7, 2019 at 7:44:03 AM UTC-7, Jeroen Demeyer wrote: > > On 2019-06-07 16:38, E. Madison Bray wrote: > > While I agree it's part of an annoying trend, this is one change I > > welcome: The Python interpreter shipped in OSX has always *always* > > been broken and unusable > >

[sage-support] Re: A genuine bug in numerical evaluation ?

Oh, and Sage with Python 3 is in pretty good shape these days. Still some doctest failures, but I think it is mostly very functional. John On Thursday, June 6, 2019 at 3:20:25 PM UTC-7, John H Palmieri wrote: > > I can confirm that it works for me on OS X with Python 3, gives the

[sage-support] Re: A genuine bug in numerical evaluation ?

I can confirm that it works for me on OS X with Python 3, gives the error you described with Python 2. On Thursday, June 6, 2019 at 2:57:08 PM UTC-7, Emmanuel Charpentier wrote: > > According to Serge Lelièvre, the proble doesn't occur when ran under a > Python3-based Sage. He advises to run

Re: [sage-devel] Re: Errors from MacOS build with Python3

docutils-0.14 > > I'll run make ptest-python3 as you suggest. > > Thanks again > > Brian > > > > On Thu, May 30, 2019 at 3:19 PM John H Palmieri > wrote: > >> >> >> On Thursday, May 30, 2019 at 2:15:12 PM UTC-7, Brian Ball wrote: >>> >&g

[sage-devel] Re: Errors from MacOS build with Python3

On Thursday, May 30, 2019 at 2:15:12 PM UTC-7, Brian Ball wrote: > > I built sage 8.7 with python 3.6. > What do you mean by "built"? Did you run "make"? If so, did it complete without error? (I would find that surprising, since "make" should build the documentation.) What does the file

[sage-devel] Are Sage library files supposed to pass when using "sage -tp --file-iterations=N FILES"?

If I run ./sage -tp --file-iterations=2 src/sage/algebras/ then I get many doctest failures. Is this expected? Is something broken when using the "--file-iterations" flag? -- sage -t src/sage/algebras/free_algebra.py # 1

Re: [sage-devel] error building pynormaliz with 8.8.beta6

On Wednesday, May 29, 2019 at 5:52:26 PM UTC-7, Michael Orlitzky wrote: > > On 5/28/19 5:09 PM, Sébastien Labbé wrote: > > > > $ cd > /home/slabbe/GitBox/sage/local/var/tmp/sage/build/pynormaliz-2.5/src > > $ strace sh congiure > > ... > > 4000 lines in total including: > > ... > >

[sage-support] Re: how to do ?

On Saturday, May 25, 2019 at 3:31:00 AM UTC-7, HG wrote: > > sage -i database_odlyzko_zeta > > doesn't work in sagemath-8.8beta6 ? > > How can I do it ? > > Please provide more details: what platform? What went wrong. It worked for me, by the way: $ ./sage -i database_odlyzko_zeta ...

[sage-support] Re: installation on OSX Mojave, Sage V. 8.7

On Friday, May 24, 2019 at 9:03:39 AM UTC-7, frank wessel wrote: > > downloaded the sage-8.7-OSX_10.11.6-x86_64.dmg (hopefully the latest) > installed the package into Applications/SageMath folder > set the SAGE_ROOT env variable in /etc/profile > You should not need to set the SAGE_ROOT

Re: [sage-devel] Would anybody like...progress bars?

There is also the "warn-long" flag: sage -t --warn-long 3.2 FILE should tell you all tests in FILE that take more than 3.2 seconds. On Thursday, May 23, 2019 at 4:05:04 PM UTC-7, Travis Scrimshaw wrote: > > sage -t --verbose (or -tp of course) > > Best, > Travis > > > On Friday, May 24,

[sage-devel] Re: Printing a matrix of large size

Did you try "print(mat.str())"? On Saturday, May 18, 2019 at 6:37:02 PM UTC-7, Kwankyu Lee wrote: > > Hi, > > If mat is a matrix of large size, it is displayed in a short form: > > sage: mat > 22 x 32 dense matrix over Finite Field of size 2 (use the '.str()' method > to see the entries) > > >

Re: [sage-support] Re: parent of permutation

On Friday, May 3, 2019 at 11:18:40 PM UTC-7, Daniel Krenn wrote: > > On 04.05.19 06:04, Andrew wrote: > > The `Permutation` function is more general. For example, the folllowing > > all work: [...] > > Thank you. But sorry, this does not answer my question. Maybe I should > be more precise:

[sage-devel] Re: CHomP

On Friday, May 3, 2019 at 10:22:25 AM UTC-7, Salvatore Stella wrote: > > Hi All, > has anyone tried installing CHomP recently? For me it fails applying > patches. > It is an old-style package and apparently it is very stale; does it > provide > any tangible speedup in

Re: [sage-devel] patchbot questions

On Tuesday, April 23, 2019 at 12:18:13 AM UTC-7, Daniel Krenn wrote: > > On 23.04.19 01:37, John H Palmieri wrote: > > I was running a patchbot successfully until some time last week. For > > reasons I don't understand, I did "git pull" on the patchbot, and now it

[sage-devel] patchbot questions

I was running a patchbot successfully until some time last week. For reasons I don't understand, I did "git pull" on the patchbot, and now it won't run with Python 2, complaining File "sage_patchbot/plugins.py", line 309 yield from names ^ SyntaxError: invalid syntax Do I

[sage-support] Re: reconnect to remote sagemath jupyter notebook?

If you're willing to use the Sage command-line interface rather than the notebook, then you might try the "screen" program, which should already be installed on linux or Mac OS X. You might remotely log in to the machine running Sage and then do "screen sage". Then you type in whatever commands

Re: [sage-support] Re: Sorting a list of variables

On Monday, April 22, 2019 at 11:03:48 AM UTC-7, slelievre wrote: > > Having defined > > sage: x = SR.var('x', 20) > sage: a = [x[11], x[8], x[10], x[9]] > > sorting by repr or by str is disappointing: > > sage: sorted(a, key=repr) > [x10, x11, x8, x9] > > sage: sorted(a,

[sage-devel] Re: python3 status report (mi-april of last python2 year)

What does sage: C Set partitions of {'a', 'c', 'b'} reveal? Is it helpful, or can it be omitted? Maybe it's good enough to do sage: C = SetPartitions(["a", "b", "c"]) sage: C.cardinality() 5 sage: sorted(C) [{{'a'}, {'b'}, {'c'}}, {{'a'}, {'b', 'c'}}, {{'a', 'b'}, {'c'}}, {{'a', 'b', 'c'}},

[sage-devel] Re: Matrix exponentials of diagonal matrices.

On Tuesday, April 16, 2019 at 8:30:13 PM UTC-7, Nils Bruin wrote: > > On Tuesday, April 16, 2019 at 8:06:06 PM UTC-7, Brian Fitzpatrick wrote: >> >> >> Is this a bug? >> >> Looks like it. The problem seems to be that "sparse matrices over SR" > aren't special cased the way dense matrices are

[sage-devel] Re: frozensets in doctests / for display in Python3

Is the printed order important? If not, you can change the doctest to something else that is actually testing something relevant, maybe like sage: 'B' in frozenset() True or sage: (define the frozenset S somehow) sage: S == frozenset(['A', 'B', 'C']) True Or if

Re: [sage-devel] Polyhedron.vertices() function call behaviour

Can you provide details of how you created the polyhedron? As David said, Q.vertices() should make a copy before returning the result, and I would like to recreate this so I can fix it. On Thursday, April 11, 2019 at 9:21:42 PM UTC-7, Narayanan Narayanan wrote: > > Thank you David. Using

Re: [sage-support] Preferred way to navigate through documentation

You should also look at the Sage tutorial (http://doc.sagemath.org/html/en/tutorial/). The 2nd page of the "guided tour" talks about "?", and there may be other things that you would find useful. On Sunday, April 7, 2019 at 5:36:18 PM UTC-7, Fan Zhang wrote: > > Thanks a lot! "?" is the

[sage-devel] Re: building documentation with python3.6 and topcom installed

What happens when you run this version of Sage and do sage: PointConfiguration.set_engine('internal') # to make doctests independent of TOPCOM sage: p = PointConfiguration([[-1,-1],[1,1],[1,0],[0,1],[0,0]]) and then if that succeeds, plot p? What if you omit the first line and just

[sage-devel] "@experimental" decorator, doctests, and py2 vs. py3

I am confused about how Sage's doctests work with a deprecation warning, for example as coming from the @experimental decorator. Here is a snippet from the top of rings/padics/padic_lattice_element.py: sage: R = ZpLC(2) doctest:...: FutureWarning: This class/method/function is marked as

[sage-devel] Re: load() function doesn't pop up a PNG viewer

On Wednesday, April 3, 2019 at 4:20:43 PM UTC-7, Yagamy Light wrote: > > > > On Thursday, 4 April 2019 01:58:09 UTC+3, John H Palmieri wrote: >> >> >> >> On Wednesday, April 3, 2019 at 3:13:43 PM UTC-7, Yagamy Light wrote: >>> >>> >

[sage-devel] Re: load() function doesn't pop up a PNG viewer

On Wednesday, April 3, 2019 at 3:13:43 PM UTC-7, Yagamy Light wrote: > > > > On Wednesday, 3 April 2019 22:42:15 UTC+3, Samuel Lelievre wrote: >> >> >> >> Le mercredi 3 avril 2019 17:43:51 UTC+2, Yagamy Light a écrit : >>> >>> # Steps to reproduce (in terms of terminal comands: >>> >>> $ cat

Re: [sage-support] Print statement vs function in Sage-py3

On Wednesday, April 3, 2019 at 10:11:19 AM UTC-7, kcrisman wrote: > > > > On Tuesday, April 2, 2019 at 6:03:23 PM UTC-4, Dima Pasechnik wrote: >> >> On Tue, Apr 2, 2019 at 10:47 PM > >> wrote: >> > >> > Hello, Sage community. >> > With the upcoming migration of Sage from Python2 to Python3,

[sage-release] Re: Sage 8.8.beta0 released

On Saturday, March 30, 2019 at 3:42:10 PM UTC-7, Volker Braun wrote: > > PS: this should now build without manually installing additional headers > on OSX 10.14, so if you have a Mojave machine that previously gave troubles > compiling Sage please try this version and report back! > It works

[sage-support] Re: Sage options not recognized.

What does "sage --version" say? On Friday, March 29, 2019 at 12:47:44 PM UTC-7, Jose Garcia wrote: > > Hi All, > > I'm trying to install a package to sage math, and I can't get sage to > recognize specific options. > > Ex > > $ sage --package fix-checksum conjecturing > sage-run received

[sage-release] Re: Sage 8.7 released

On Wednesday, March 27, 2019 at 2:54:48 PM UTC-7, Simon King wrote: > > Hi John, hi Samuel, > > On 2019-03-27, John H Palmieri > wrote: > >> Regarding the failures in src/sage/tests/modular_group_cohomology.py > >> related to the optional package p_group_cohom

Re: [sage-release] Sage 8.7 released

On Wednesday, March 27, 2019 at 5:02:23 AM UTC-7, Samuel Lelievre wrote: > > Sun 2019-03-24 00:41 UTC, Volker Braun: > > > > The "master" git branch has been updated to Sage-8.7. > > On Debian 9.8 ("stretch"), from a fresh git clone, building > python2-based SageMath with as many optional

[sage-devel] Re: How docstrings generate html

On Sunday, March 24, 2019 at 12:21:43 PM UTC-7, Chaman Agrawal wrote: > > I was trying to contribute through a ticket related to documentation but I > am not sure how docstrings are generating HTML and have doubts. > 1) It is ignoring all the function of with names like __function_name__ >

Re: [sage-devel] Re: how does the res/mod in "geng" work?

It's part of nauty. > On Thu, Mar 21, 2019 at 9:58 PM John H Palmieri > wrote: > >> >> >> On Thursday, March 21, 2019 at 9:38:03 PM UTC-7, Ai Bo wrote: >>> >>> Saw this in the document: >>> res/mod : only generate subset res out of subsets 0..mod-1

[sage-devel] Re: how does the res/mod in "geng" work?

On Thursday, March 21, 2019 at 9:38:03 PM UTC-7, Ai Bo wrote: > > Saw this in the document: > res/mod : only generate subset res out of subsets 0..mod-1 > It would help if you gave some context for this. I'm guessing that most Sage users won't know what "geng" is. I certainly didn't. I found

Re: [sage-release] Re: Sage 8.7.rc0 released

On Wednesday, March 20, 2019 at 9:17:37 AM UTC-7, Dima Pasechnik wrote: > > so you need to rebuild sagelib with new libvpx. > In general after a major system update it's best to "make distclean" > and rebuild from scratch. > > Or you can touch pyx files which depend upon libvpx and run make,

Re: [sage-support] yasm can not be installed/compiled

What are the modification dates and times for the files in the directory /apps/srv01/pmt/pmtfh/sage/sage-8.6/local/var/tmp/sage/build/yasm-1.3.0.p0 Maybe you should run 'make' again, which will regenerate this directory, and then check the times on the files. Are any of them in the future?

Re: [sage-devel] Re: internet tests failing

On Friday, March 15, 2019 at 3:31:33 AM UTC-7, Dima Pasechnik wrote: > > On Thu, Mar 14, 2019 at 7:51 PM John H Palmieri > wrote: > > > > I'm seeing the same failure on a Mac running the most recent OS X. I > have openssl 1.1.1a installed on this machine, and

[sage-devel] Re: pretty print latex doctest error

On Thursday, March 14, 2019 at 1:46:38 PM UTC-7, kcrisman wrote: > > I just ran the following command, and amazingly got only one timeout and > one error. The rest is fine. > > ./sage -tp 3 -T 600 --optional=sage,python2,latex src/sage > >

[sage-devel] Re: internet tests failing

I'm seeing the same failure on a Mac running the most recent OS X. I have openssl 1.1.1a installed on this machine, and I see the error in Sage. Then I did './sage -i openssl' and './sage -f python2', and I still see the error. The Python 2 log file does not list ssl among the modules which

[sage-devel] Recommendation for Mac OS X users on Sage's cutting edge

For those of you who use OS X and also like to do incremental upgrades to Sage's most recent beta release, I would suggest running 'make distclean' and then 'make'. Why? Previous versions of Sage have broken file manifests for its packages – not broken on linux, only OS X – so package

Re: [sage-devel] error while building sage

In case others have this problem before the next beta is released: not just sphinx is missing as a dependency, but also ppl. You should do ./sage -i sphinx ppl followed by make On Tuesday, March 5, 2019 at 2:56:00 AM UTC-8, Dima Pasechnik wrote: > > Thanks, you found a bug in Sage -

[sage-devel] Build docs (even more) in parallel?

Would it be possible to generate all of the plots in the reference manual in parallel? For example, the plots in local/share/doc/sage/inventory/en/reference/plotting/sage/graphs seem to be generated serially, and this is a bottleneck in building the reference manual. Maybe instead of

Re: [sage-devel] What to do with the sys.path security patch?

On Thursday, February 28, 2019 at 9:16:19 AM UTC-8, E. Madison Bray wrote: > > > I suggest a middle ground: I don't believe this behavior should be > tested in Sage's test suite, because this is a question about the > Python interpreter's behavior, not Sage. The possibility of running > Sage

[sage-devel] Re: Inequalities in Z/nZ

On Wednesday, February 27, 2019 at 3:14:53 PM UTC-8, Nils Bruin wrote: > > On Wednesday, February 27, 2019 at 2:17:06 PM UTC-8, John H Palmieri wrote: >> >> Why does Sage allow inequalities in Z/nZ? >> > > I'm pretty sure that it's a historical artifact from

[sage-devel] Inequalities in Z/nZ

Why does Sage allow inequalities in Z/nZ? sage: Z3 = Integers(3) sage: a = Z3(4) sage: b = Z3(2) sage: a < b True sage: a < 3 False While < may make sense in the set {0, 1, 2, ..., n-1}, it doesn't make sense in the ring Z/nZ: sage: Z3(1) < Z3(2) True sage: 1+Z3(1) < 1+Z3(2) False sage:

[sage-devel] Re: Error building Sage

Please try this: ./sage -f zlib ./sage -f python2 python3 make and see if that fixes the problem. (Apologies for not responding in French.) On Wednesday, February 27, 2019 at 1:52:02 PM UTC-8, Quentin Hillebrand wrote: > > En compilant avec make j'obtiens j'obtiens une erreure lors de la >

[sage-support] Re: How to find coordinate vector

I would define the span over the integers differently, using "span_of_basis" to make sure it uses the basis you specify: sage: V = ZZ^2 sage: W = V.span_of_basis(R) sage: W Free module of degree 2 and rank 2 over Integer Ring User basis matrix: [1 3] [1 0] sage: W.coordinates([0,3]) [1, -1]

Re: [sage-release] Sage 8.7.beta3 released

On Saturday, February 9, 2019 at 7:08:36 PM UTC-8, Justin C. Walker wrote: > > > > > On Feb 8, 2019, at 11:27 , Volker Braun > wrote: > > > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at >

[sage-support] Re: solution of a 4th degree equation is real despite containing I but causes trouble

Or range(abs(t))? Then if there is some numerical noise leading to a tiny imaginary part (your t might be evaluated to 2.573037896825689 - 4.365411232224172e-17*I for example), abs(t) won't care. On Wednesday, February 20, 2019 at 10:42:32 AM UTC-8, John H Palmieri wrote: > > How about

[sage-support] Re: solution of a 4th degree equation is real despite containing I but causes trouble

How about range(0, RR(t))? On Wednesday, February 20, 2019 at 10:11:14 AM UTC-8, Michael Beeson wrote: > > Oh, and range(0,n(t)) also crashes. > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop

[sage-support] Re: solve() behavior

On Tuesday, February 19, 2019 at 8:56:50 AM UTC-8, Michael Beeson wrote: > > When I try to reproduce Eric's post, I get an error message about an > unexpected keyword argument > (maybe my version of Sage is too old.) But look at this: > > sage:

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

On one of my machines running OS X Mojave, when I run 'make', the pip installation fails, saying ModuleNotFoundError: No module named 'zlib' That's when the solution is ./sage -f zlib python2 python3 make On Monday, February 18, 2019 at 12:58:19 PM UTC-8, John H Palmieri wrote

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

UTC+11, John H Palmieri wrote: >> >> Can you post the end of the file logs/pkgs/pip-18.1.log? The last 30 >> lines or so? Or post the whole file if you can. >> >> The log from after the failed make is s below. It says that > No record that 'pip' was ever ins

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

On Monday, 18 February 2019 17:46:24 UTC+11, John H Palmieri wrote: >> >> Please try: >> >> ./sage -f zlib >> ./sage -f python2 >> ./sage -f python3 >> >> and if those work, try 'make' again. >> >> John >> >> >> >>

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

Sorry, that's wrong. Try: ./sage -f zlip <-- This is the correction ./sage -f python2 ./sage -f python3 make See also https://trac.sagemath.org/ticket/26899. John On Sunday, February 17, 2019 at 10:40:59 PM UTC-8, John H Palmieri wrote: > > Please try: > > ./sage -f zip >

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

Please try: ./sage -f zlib ./sage -f python2 ./sage -f python3 and if those work, try 'make' again. John On Sunday, February 17, 2019 at 6:11:51 PM UTC-8, Andrew wrote: > > I have been unable to compile sage for a while on both an imac and a > macbook pro that are running mojave (clearly

[sage-devel] Re: Unable to compile sage 8.7.beta3 on mojave...

Please try: ./sage -f zip ./sage -f python2 ./sage -f python3 and if those work, try 'make' again. John On Sunday, February 17, 2019 at 6:11:51 PM UTC-8, Andrew wrote: > > I have been unable to compile sage for a while on both an imac and a > macbook pro that are running mojave (clearly my

Re: [sage-release] Sage 8.7.beta1 released

On Tuesday, February 5, 2019 at 4:53:02 PM UTC-8, Justin C. Walker wrote: > > > > > On Jan 26, 2019, at 16:18 , Volker Braun > wrote: > > > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the self-contained source tarball is at >

Re: [sage-devel] sage install slow or hanging on bleach?

ch-3.0.2.tar.gz > > Is this what you wanted to see? > > (Also, would it not say 'invalid checksum' because I hit ctrl+c to abort > whatever download it was doing?) > > > On Monday, February 4, 2019 at 12:39:10 PM UTC-6, John H Palmieri wrote: >> >> Actually, don't do th

Re: [sage-devel] sage install slow or hanging on bleach?

Actually, don't do that yet. What do you get with $ ls -l upstream/bleach-3.0.2.tar.gz It shouldn't say "Invalid checksum": that is a standard package and a valid tarball should be included with the Sage distribution. On Monday, February 4, 2019 at 10:36:57 AM UTC-8, John H Palm

Re: [sage-devel] sage install slow or hanging on bleach?

Try downloading bleach-3.0.2.tar.gz separately and put it in the "upstream" directory in Sage. Then run "./sage -i bleach". (If I try the link http://mirrors.mit.edu/sage/spkg/upstream/bleach/bleach-3.0.2.tar.gz

[sphinx-users] Re: hard to identify offending line in source file

On Tuesday, January 29, 2019 at 1:01:32 PM UTC-8, Phillip Feldman wrote: > > I'm new to Sphinx, so perhaps this is a stupid question. > > When I see an error message like the following from Sphinx, it is unclear > to me which line of the source file is triggering the error: > > docstring of

[sage-devel] Re: spkgs dependencies graph

Cool, and then you can call Poset(digraph_spkg()). On Tuesday, January 29, 2019 at 12:56:07 PM UTC-8, Frédéric Chapoton wrote: > > Quick tentative, not smooth: > > from sage.misc.package import * > > > > > def digraph_spkg(): > """ > digraph > """ > opts = {} > > > local =

[sage-release] Re: Sage 8.7.beta1 released

And now the documentation builds with Python 3! (This is due to #26949 plus a lot of prep work organized by Frédéric.) On Saturday, January 26, 2019 at 4:18:24 PM UTC-8, Volker Braun wrote: > > As always, you can get the latest beta version from the "develop" git > branch. Alternatively, the

Re: [sage-devel] How is package installation/uninstallation supposed to work?

On Wednesday, January 23, 2019 at 9:58:19 AM UTC-8, E. Madison Bray wrote: > > On Wed, Jan 23, 2019 at 6:26 PM John H Palmieri > wrote: > > > > > > > > On Wednesday, January 23, 2019 at 9:11:17 AM UTC-8, John H Palmieri > wrote: > >> > &g

Re: [sage-devel] How is package installation/uninstallation supposed to work?

On Wednesday, January 23, 2019 at 9:11:17 AM UTC-8, John H Palmieri wrote: > > > > On Wednesday, January 23, 2019 at 9:06:45 AM UTC-8, John H Palmieri wrote: >> >> >> >> On Wednesday, January 23, 2019 at 8:57:24 AM UTC-8, John H Palmieri wrote: >>> &g

Re: [sage-devel] How is package installation/uninstallation supposed to work?

On Wednesday, January 23, 2019 at 9:06:45 AM UTC-8, John H Palmieri wrote: > > > > On Wednesday, January 23, 2019 at 8:57:24 AM UTC-8, John H Palmieri wrote: >> >> >> >> On Wednesday, January 23, 2019 at 3:59:41 AM UTC-8, E. Madison Bray wrote: >>&g

Re: [sage-devel] How is package installation/uninstallation supposed to work?

On Wednesday, January 23, 2019 at 8:57:24 AM UTC-8, John H Palmieri wrote: > > > > On Wednesday, January 23, 2019 at 3:59:41 AM UTC-8, E. Madison Bray wrote: >> >> On Tue, Jan 22, 2019 at 8:30 PM John H Palmieri >> wrote: >> > >> > Here is

Re: [sage-devel] How is package installation/uninstallation supposed to work?

On Wednesday, January 23, 2019 at 3:59:41 AM UTC-8, E. Madison Bray wrote: > > On Tue, Jan 22, 2019 at 8:30 PM John H Palmieri > wrote: > > > > Here is the situation: I've been playing around with new versions of > Sphinx. If I've installed a new version and then g

[sage-devel] How is package installation/uninstallation supposed to work?

Here is the situation: I've been playing around with new versions of Sphinx. If I've installed a new version and then go back to an old version, the directory local/lib/python2.7/site-libraries/sphinx/ is not removed and then recreated, but instead the changed files are reinstalled, leaving

[sage-devel] Re: Startup time improvement in 8.6

On Thursday, January 17, 2019 at 12:11:03 PM UTC-8, Timo Kaufmann wrote: > > When packaging sage 8.6, I noticed that startup felt unusually fast. So I > averaged the startup time over 100 runs: > > ``` > for i in {1..100}; do > Are the file names interchanged here? > "sage-8.5/bin/sage"

[sage-devel] Re: Delaying 8.5 or fast-tracking 8.6?

UTC-8, Emmanuel Charpentier wrote: > > Even considering the pivotal rôle of polynomials and fraction fields > thereof ? > > Le jeudi 20 décembre 2018 20:47:03 UTC+1, John H Palmieri a écrit : >> >> Critical but it's not a blocker, in my opinion. >> >> >>

[sage-devel] Re: Delaying 8.5 or fast-tracking 8.6?

Critical but it's not a blocker, in my opinion. On Thursday, December 20, 2018 at 11:36:15 AM UTC-8, Emmanuel Charpentier wrote: > > This seems > seems to be a showstopper, enough to trump the best laid out plans of mice, > men

[sage-devel] Re: Changes in polynomial quotient ring are intended?

On Thursday, December 20, 2018 at 9:49:38 AM UTC-8, Nils Bruin wrote: > > On Wednesday, December 19, 2018 at 11:11:25 AM UTC-8, Jörg-Volker wrote: >> >> Hi, >> >> in version 8.4 this example doesn't work anymore as it did at least until >> version 8.2: >> varl = ['x0', 'x1', 'x2', 'x3'] >> B =

Re: [sage-release] Sage 8.5.rc1 released

With the workaround, when you set OBJC_DISABLE_INITIALIZE_FORK_SAFETY, it must be set to YES, not yes. Which way did you try it? John On Monday, December 17, 2018 at 1:56:38 PM UTC-8, Justin C. Walker wrote: > > > > > On Dec 16, 2018, at 14:35 , Volker Braun > wrote: > > > > As always,

<    1   2   3   4   5   6   7   8   9   10   >