Re: [sage-devel] ask.sagemath.org down?

gt; On 16/01/16 13:40, William Stein wrote: > > On Sat, Jan 16, 2016 at 8:39 AM, John H Palmieri <jhpalm...@gmail.com > > wrote: > >> It looks like ask.sagemath.org is down, and has been for several days. > (Or > >> is it just me?) If it's not just

[sage-devel] Re: Unexpected solution of: Solve(x==sqrt(x), x)

On Wednesday, January 13, 2016 at 12:59:08 PM UTC-8, John Mesh wrote: > > The following is not what I expect: > > sage: x = var('x') > sage: assume(x, 'real') > sage: solve([x == sqrt(x) + 3], x) > [x == sqrt(x) + 3] > > Expected result: x = (7 + sqrt(13))/2 > Try sage: solve([x == sqrt(x) +

Re: [sage-devel] UniqueRepresentation in FormalSums

On Wednesday, January 13, 2016 at 1:03:15 PM UTC-8, Martin R wrote: > > > > Am Mittwoch, 13. Januar 2016 21:57:00 UTC+1 schrieb John H Palmieri: >> >> >> >> On Wednesday, January 13, 2016 at 12:43:25 PM UTC-8, Martin R wrote: >>> >>> To under

Re: [sage-devel] UniqueRepresentation in FormalSums

On Wednesday, January 13, 2016 at 12:43:25 PM UTC-8, Martin R wrote: > > To understand the difference between ‘is’ and ‘==‘ may require some >> background in programming. >> >> Specifically, “a==b” evaluates to “True” if the objects ‘a’ and ‘b’ >> “evaluate to the same *value*”, while “a is b”

Re: [sage-devel] cython string problem

On Sunday, January 10, 2016 at 9:26:53 AM UTC-8, Daniel Krenn wrote: > > On 2016-01-10 15:18, Vincent Delecroix wrote: > > Would better to post to sage-support. > > F'up set > > > What about doing the test in the console? You can also change the > > doctest to > > > > m2.__repr__() >

Re: [sage-devel] Re: Jupyter notebook by default?

On Sunday, December 20, 2015 at 8:16:44 PM UTC-8, Nils Bruin wrote: > > On Sunday, December 20, 2015 at 2:12:57 PM UTC-10, William wrote: >> >> It will be much easier for our users to actually *use* a converter if >> we delay changing the defaults until after such a converter is >> written.

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

On Sunday, December 13, 2015 at 2:43:45 AM UTC-8, Volker Braun wrote: > > On Sunday, December 13, 2015 at 6:51:02 AM UTC+1, John H Palmieri wrote: >> >> error: >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool:

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

Building from scratch on OS X 10.11 fails for me. In the singular log: error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: changing install names or rpaths can't be redone for:

[sage-support] Re: view(g) where g is graph: does not respect colors

On Tuesday, December 1, 2015 at 9:40:18 AM UTC-8, Pedro Cruz wrote: > > The following code (sage 6.9): > > sage: g = graphs.PetersenGraph() > sage: g.set_latex_options(vertex_color='green') > sage: view(g) > > > produces a black-and-white graph. > Can you use "g.plot()" instead? If so, "g.plot?"

[sage-devel] Re: Who uses SAGE64

On Sunday, November 29, 2015 at 1:47:26 PM UTC-8, Volker Braun wrote: > > François asked me whether we still use the SAGE64 sections that are > copy-pasted into many spkg-install files; All I know is that no buildbot > slave is testing it so surely its broken. Or can anybody report success? Is

[sage-devel] Re: should "foo?" print TESTS: blocks or omit them?

On Saturday, November 7, 2015 at 2:01:17 AM UTC-8, Volker Braun wrote: > > I don't really care about whether to display TESTS:: or not, but we really > should have a proper parser for our docstring style. This ticket adds yet > another regex hack. E.g. sphinxcontrib-napoleon is an example for

Re: [sage-devel] upgrading to matplotlib

With the current version, running grep -R 'width and height must' local/lib/python/site-packages/matplotlib* finds a match. What happens if you do the same with the new version? On Monday, November 9, 2015 at 10:22:12 AM UTC-8, François wrote: > > I tried a few already but I can try some

Re: [sage-devel] upgrading to matplotlib

Oh, and in original tarball, it's in 'src/_backend_agg.cpp'. John On Monday, November 9, 2015 at 11:09:49 AM UTC-8, John H Palmieri wrote: > > With the current version, running > > grep -R 'width and height must' > local/lib/python/site-packages/matplotlib* > > finds

Re: [sage-devel] upgrading to matplotlib

less than" and "below" in the src directory and didn't find anything useful. John On Monday, November 9, 2015 at 1:51:42 PM UTC-8, François wrote: > > On 11/10/15 08:12, John H Palmieri wrote: > > Oh, and in original tarball, it's in 'src/_backend_agg.cpp'. > >

[sage-support] Re: How to save the output of view locally (and not open the output)?

On Saturday, November 7, 2015 at 1:34:49 PM UTC-8, slabbe wrote: > > This opens a pdf: > > sage: g = graphs.PetersenGraph() > sage: s = latex(g) > sage: view(s, tightpage=True) > > But is there a way to just save that pdf file locally and not open it? > Until you quite the Sage session, the

[sage-devel] should "foo?" print TESTS: blocks or omit them?

At http://trac.sagemath.org/ticket/19503, we have a branch which implements the omission of 'TESTS:' blocks in docstrings when you do 'foo?' (and optionally, but this is not the default behavior, it can omit them in the reference manual). There are pros and cons to this: for some time, our

Re: [sage-support] TAB completion

On Thursday, November 5, 2015 at 3:40:01 PM UTC-8, William wrote: > > On Thu, Nov 5, 2015 at 3:29 PM, Justin C. Walker > wrote: > > Hi, > > > > In the distant past, I knew how to configure Sage to handle TAB > completion this way: > > - one TAB: complete if unique

Re: [sage-support] TAB completion

On Thursday, November 5, 2015 at 5:03:27 PM UTC-8, William wrote: > > On Thu, Nov 5, 2015 at 4:02 PM, John H Palmieri <jhpalm...@gmail.com > > wrote: > > > > > > On Thursday, November 5, 2015 at 3:40:01 PM UTC-8, William wrote: > >> > >> On

[sage-devel] Re: Definition of multifactorial #5415

On Friday, October 30, 2015 at 8:50:42 AM UTC-7, Dima Pasechnik wrote: > > > > On Friday, 30 October 2015 05:38:56 UTC, prateek sharma wrote: >> >> >> It should be like >> a=42 >> k=3 >> sage: a.multifactorial(k) >> > > I told you to display the source code for this function, as this is what >

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

How important is it that the user see any of these? Should our documentation build hide these labels altogether? Should it hide "TESTS" blocks? Same questions when you ask for interactive help via "foo?". John On Thursday, October 29, 2015 at 5:54:26 AM UTC-7, Nathann Cohen wrote: > >

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

On Thursday, October 29, 2015 at 8:59:04 AM UTC-7, Nathann Cohen wrote: > > > How important is it that the user see any of these? Should our > documentation > > build hide these labels altogether? Should it hide "TESTS" blocks? Same > > questions when you ask for interactive help via "foo?".

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

On Thursday, October 29, 2015 at 10:12:59 AM UTC-7, Nathann Cohen wrote: > > > Yep! That's why I called it "not tested". In my opinion, the only > > reasonable change would be > > > > " # not tested" > " # broken" > > > > That would probably create an even more accurate

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

On Thursday, October 29, 2015 at 10:07:33 AM UTC-7, Nathann Cohen wrote: > > Hello, > > > Since we can already detect doctests, and among those we can already > detect > > the various doctest flags, we should be able to hide those flags. The > TESTS > > blocks are a different situation. If

[sage-support] Re: How can one recompile a standard package (without rebuilding the whole thing) ?

On Wednesday, October 28, 2015 at 10:19:51 AM UTC-7, Emmanuel Charpentier wrote: > > Case in point : Trac#19469 . This > ticket will solve an annoying quirk un the Ipython notebook. > > I tested it successfully on one installation, by recompiling the

[sage-support] Re: How can one recompile a standard package (without rebuilding the whole thing) ?

o that it knows to build the new one instead of the old one. John > > Thanks, John ! > > Le mercredi 28 octobre 2015 18:32:06 UTC+1, John H Palmieri a écrit : >> >> >> >> On Wednesday, October 28, 2015 at 10:19:51 AM UTC-7, Emmanuel Charpentier >> w

[sage-support] Re: building sage from source on OSX 10.11 El Capitan

On Thursday, October 22, 2015 at 12:57:08 PM UTC-7, Karl Rubin wrote: > > I upgraded to El Capitan OSX 10.11 on my iMac before I knew that this > would kill my sage installation. I see that there was a ticket about this > (#19370) that is now closed/fixed. How can I get the corrected source

[sage-devel] Re: Sage on OS X: El Capitan

As you said in another thread, look at the big red message at the top of http://www.sagemath.org/download-mac.html which points to http://trac.sagemath.org/ticket/19370 The latest beta version of Sage should build on OS X 10.11. It has a serious limitation: you can't move the

[sage-support] Re: Graph.clique_complex()

On Friday, October 2, 2015 at 8:50:12 PM UTC-7, Selva Raja S wrote: > > > clique_complex() does not shows facets > > > > *for example*sage: > g=Graph({1:[2,5,6,3,4],2:[7,3,5,4],3:[8,4,5],4:[9,5],5:[10]}) > sage: g.clique_complex() > Simplicial complex with 10 vertices and 6 facets > You have

[sage-devel] Running 'make' twice triggers a gcc rebuild

Anyone seen this? On one OS X machine, with two different installations of Sage 6.9.rc0 (one built by upgrading earlier versions, one built from a fresh tarball), if I do this: $ make distclean $ make $ make then the second time, although it should do almost nothing, it rebuilds gcc. I

Re: [sage-devel] Re: Checker function for integer parameters

On Saturday, September 26, 2015 at 10:55:57 AM UTC-7, Jori Mäntysalo wrote: > > On Sat, 26 Sep 2015, Travis Scrimshaw wrote: > > > I would use: > > > > if n not in ZZ: > >raise ValueError(...) > > Seems easy. But to make sure: does this work in all cases? I.e. raw Python > ints, Sage

Re: [sage-devel] Re: Docs: Symbols and `self`

On Friday, September 25, 2015 at 7:47:23 AM UTC-7, William wrote: > > On Fri, Sep 25, 2015 at 4:38 AM, Eric Gourgoulhon > wrote: > > Hi, > > > > Le vendredi 25 septembre 2015 08:45:34 UTC+2, Jori Mäntysalo a écrit : > >> > >> More on docstrings: > >> > >> "The

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

Please try the latest Sage prerelease (6.9.rc0, available here: http://files.sagemath.org/devel/index.html) should build with Xcode 7, so I hope it builds with OS X 10.11. John On Friday, September 18, 2015 at 8:14:44 AM UTC-7, John H Palmieri wrote: > > > > On Friday, Septem

Re: [sage-devel] Re: About abbreviation in function names

On Wednesday, September 23, 2015 at 10:43:43 AM UTC-7, Dima Pasechnik wrote: > > > > On Wednesday, 23 September 2015 10:32:08 UTC-7, Thierry > (sage-googlesucks@xxx) wrote: >> >> Hi, >> >> On Wed, Sep 23, 2015 at 06:46:10PM +0200, Jeroen Demeyer wrote: >> > On 2015-09-23 18:44, Dima Pasechnik

[sage-devel] Re: access denied on git

On Monday, September 21, 2015 at 5:54:05 PM UTC-7, Mike Zabrocki wrote: > > I mistakenly installed XCode 7 and so to save myself I started working on > a fresh copy of sage where I don't do too much compiling. > Have you tried running Xcode once? It will install some command-line tools, and

Re: [sage-devel] Sage in Mac OSX 11.11 (El Capitan)

On Friday, September 18, 2015 at 2:01:24 AM UTC-7, Juan Luis Varona wrote: > > Actually, xcode 7 were released yesterday. > > I can confirm that again sage 6.8 cannot be compiled in mac os x 10.11 > with xcode 7. > > Juan Luis > We are tracking build issues with Xcode 7 here:

Re: [sage-release] Sage 6.9.beta7 released

On Thursday, September 17, 2015 at 11:47:49 AM UTC-7, Justin C. Walker wrote: > > > On Sep 17, 2015, at 05:07 , 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-devel] Problems with latest Xcode on OS X

I just updated my command-line tools and Xcode to version 7.0 (released today, I think). When I tried to build the latest beta of Sage from scratch, the following packages did not build: - ecm: log file http://www.math.washington.edu/~palmieri/Sage/ecm-6.4.4.log - gsl: log file

[sage-devel] Re: is python a prereq for Sage?

On Friday, September 11, 2015 at 10:14:55 AM UTC-7, kcrisman wrote: > > > Python >= 2.6 is required >> >> > Since when? At the very least our documentation for installation/whatever > should be changed. (!) > > That is "not good", for some value of good. Plus, what was the rationale? >

[sage-devel] help with mod 2 matrices

This is probably easy to fix, but I don't know how: sage: id = identity_matrix(GF(2), 1) sage: id.augment(id) # works [1 1] sage: id.augment(id.sparse_matrix()) # doesn't --- TypeError

Re: [sage-devel] Should we still support old-style packages?

On Thursday, September 10, 2015 at 3:36:37 AM UTC-7, Jeroen Demeyer wrote: > > Let's try to summarize what we have so far. > > I am going to ignore responses of the form "just port all/some packages > to new-style". That's certainly a good thing to do, but it doesn't > answer the question.

Re: [sage-devel] Should we still support old-style packages?

On Thursday, September 10, 2015 at 8:45:26 AM UTC-7, John H Palmieri wrote: > > > > On Thursday, September 10, 2015 at 3:36:37 AM UTC-7, Jeroen Demeyer wrote: >> >> Let's try to summarize what we have so far. >> >> I am going to ignore responses of t

[sage-devel] Re: Sage in Mac OSX 11.11 (El Capitan)

On Thursday, September 10, 2015 at 4:45:14 PM UTC-7, Juan Luis Varona wrote: > > > Apple released macosx 10.11-"el capitan" (golden master) yesterday. It > will be freely available for everybody in september 30. > > I have tried with both > *sage-6.8-x86_64-Darwin-OSX_10.10_x86_64.dmg >

[sage-devel] progress on simplicial complexes (or "What I did on my summer vacation")

I have been working on improving Sage's capabilities with simplicial complexes. With the changes at #19179, #6101, and #6102 (all ready for review), we now have - chain homotopies - cup products (with field coefficients) - cohomology as a FiniteDimensionalAlgebra (with field coefficients) -

[sage-combinat-devel] progress on simplicial complexes (or "What I did on my summer vacation")

I have been working on improving Sage's capabilities with simplicial complexes. With the changes at #19179, #6101, and #6102 (all ready for review), we now have - chain homotopies - cup products (with field coefficients) - cohomology as a FiniteDimensionalAlgebra (with field coefficients) -

[sage-devel] Re: Should we still support old-style packages?

I think that we should try to support old-style packages. Given that many of them are broken, and given that there are only 30 optional old-style packages (at least on http://files.sagemath.org/spkg/optional/), we can just look at them and white-list the ones that work and/or are not ancient.

Re: [sage-devel] Re: Should we still support old-style packages?

On Wednesday, September 9, 2015 at 1:24:09 PM UTC-7, Jeroen Demeyer wrote: > > On 2015-09-09 22:17, Thierry wrote: > > sorry for not participating actively to this long thread, i am currently > > pretty far from computers. Let me just mention that this discussion > > already appears some time

Re: [sage-devel] Re: Should we still support old-style packages?

On Wednesday, September 9, 2015 at 10:09:21 AM UTC-7, Jeroen Demeyer wrote: > > On 2015-09-09 17:06, John H Palmieri wrote: > > I think that we should white-list at least some of these, and also try > > to convert some of them (all of them?) to new-style packages. Same

Re: [sage-devel] Re: Should we still support old-style packages?

convert over. I will also be handling cluster_seed. > > Best, > Travis > > > On Wednesday, September 9, 2015 at 12:25:53 PM UTC-5, John H Palmieri > wrote: >> >> >> >> On Wednesday, September 9, 2015 at 10:09:21 AM UTC-7, Jeroen Demeyer >> wrote:

Re: [sage-devel] Re: Should we still support old-style packages?

On Wednesday, September 9, 2015 at 10:14:44 AM UTC-7, Nathann Cohen wrote: > > > That's of course a noble goal, but it doesn't answer the question about > what > > to do on the short term (unless you volunteer to port all packages > before > > the next Sage release). > > Is there a list of

[sage-devel] Re: TAB, the patchbot and trac

On Sunday, September 6, 2015 at 9:31:11 AM UTC-7, Nathann Cohen wrote: > > would it be possible to forbid the TAB character in the trac description >> field, or to strip it somehow at user input ? >> >> The reason is that any TAB character will prevent the patchbot from >> parsing correctly

[sage-devel] Does python pass its test suite on any platform?

At least a while ago, Sage's Python failed its test suite on most (all?) platforms. Is this still true? If you're willing, please try sage -f -c python2 and report the results. For me, it fails on OS X. -- John -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Re: Creating a Tutorial from a Worksheet mentions beautifulsoup package

On Thursday, August 27, 2015 at 1:50:29 PM UTC-7, Jeroen Demeyer wrote: On 2015-08-27 22:29, John H Palmieri wrote: Basically, all of the old-style packages are no longer easily available, just the new-style ones. This is not ideal, I think, but it was a solution to the problem

[sage-devel] Re: Creating a Tutorial from a Worksheet mentions beautifulsoup package

Also, sage -i beautifulsoup will print the message You can find further packages at http://files.sagemath.org/spkg/; and you can find a beautifulsoup spkg there. Basically, all of the old-style packages are no longer easily available, just the new-style ones. This is not ideal, I think, but it

Re: [sage-devel] Re: Creating a Tutorial from a Worksheet mentions beautifulsoup package

On Thursday, August 27, 2015 at 2:54:28 PM UTC-7, John H Palmieri wrote: On Thursday, August 27, 2015 at 1:50:29 PM UTC-7, Jeroen Demeyer wrote: On 2015-08-27 22:29, John H Palmieri wrote: Basically, all of the old-style packages are no longer easily available, just the new-style

[sage-devel] Re: heisenbugs and heisenerrors while building docs with -jN for N1 ?

On Tuesday, August 25, 2015 at 10:55:01 PM UTC-7, Dima Pasechnik wrote: On Tuesday, 25 August 2015 20:43:43 UTC-7, John H Palmieri wrote: I'd say that the problem is the error-reporting: there was certainly an error at least one docstring, it was just reporting the wrong one. I didn't

[sage-devel] Re: is_Parent(NN) gives False

On Wednesday, August 26, 2015 at 3:14:03 PM UTC-7, Nils Bruin wrote: On Wednesday, August 26, 2015 at 2:34:33 PM UTC-7, John H Palmieri wrote: Is this a valid way to proceed? sage: sage: NN.parent() class

[sage-devel] Re: is_Parent(NN) gives False

Is this a valid way to proceed? sage: sage: NN.parent() class 'sage.rings.semirings.non_negative_integer_semiring.NonNegativeIntegerSemiring_with_category' sage: import sage.structure.parent sage: sage.structure.parent.Parent in NN.parent().mro() True John On Wednesday, August 26, 2015 at

[sage-devel] Re: heisenbugs and heisenerrors while building docs with -jN for N1 ?

I'd say that the problem is the error-reporting: there was certainly an error at least one docstring, it was just reporting the wrong one. I didn't see any evidence of docbuilding itself being flaky. John On Tuesday, August 25, 2015 at 8:05:23 PM UTC-7, Dima Pasechnik wrote: thanks to

[sage-devel] Re: Should sage -i install *dependencies* of packages?

On Tuesday, August 18, 2015 at 6:49:47 AM UTC-7, Volker Braun wrote: Whats the use case of attempting to install a package without dependencies? I can't think of any. I'm not sure I can come up with very compelling examples, but if I've modified some package on which gcc depends, but I

Re: [sage-devel] Should sage -i install *dependencies* of packages?

On Monday, August 17, 2015 at 2:34:19 PM UTC-7, Jeroen Demeyer wrote: On 2015-08-17 19:01, William Stein wrote: Let's at least establish what people are likely to think sage -i already is (after 10+ years of Sage). I guess this is one of the questions: should Sage users be encouraged

[sage-devel] Re: using lower case to name functionality/constructor after a person?

On Friday, July 31, 2015 at 2:26:59 AM UTC-7, Dima Pasechnik wrote: On Friday, 31 July 2015 10:22:50 UTC+1, Nathann Cohen wrote: I prefer lower case (you don't want to miss a method in tab-completion because of case). I swear I spent 15 minutes last night looking for graphs.Chang* !

[sage-devel] Re: using lower case to name functionality/constructor after a person?

On Friday, July 31, 2015 at 7:44:50 AM UTC-7, John H Palmieri wrote: On Friday, July 31, 2015 at 2:26:59 AM UTC-7, Dima Pasechnik wrote: On Friday, 31 July 2015 10:22:50 UTC+1, Nathann Cohen wrote: I prefer lower case (you don't want to miss a method in tab-completion because of case

[sage-support] Re: Building SageMath 6.8 from source on 32-bit Ubuntu 15.04

Did you try this: Note: incremental documentation builds sometimes cause spurious error messages. To be certain that these are real errors, run make doc-clean first and try again. John On Monday, July 27, 2015 at 2:57:08 AM UTC-7, Brenton wrote: Hi, I've been downloading the latest

[sage-release] Re: Sage 6.8.beta7 released

A doctest error: sage -t --long --warn-long 49.8 src/sage/structure/dynamic_class.py ** File src/sage/structure/dynamic_class.py, line 354, in sage.structure.dynamic_class.dynamic_class_internal Failed example:

[sage-devel] Re: Build system changes in 6.8.beta7

On Friday, July 3, 2015 at 12:41:02 AM UTC-7, Jeroen Demeyer wrote: Hello all, There were some important changes to the Sage build system in 6.8.beta7: * All logs of running make will appear in install.log, including the logs of the documentation and the Sage library build. Nothing

Re: [sage-support] confirm sagenb live doc behavior

On my Mac using Safari or Firefox, if I run sage and then start the notebook, live cells in the documentation work just fine. (On the other hand, if I go to sagenb.org, log in, click Help and open up a live reference manual page, I get a green block cursor after I evaluate a cell, but it never

Re: [sage-devel] Automatic test of optional packages+updates

On Sunday, June 14, 2015 at 7:41:32 AM UTC-7, Nathann Cohen wrote: CHomP gets used by Sage if the system detects its presence. And then it leads to doctest errors. It should not: do you have an example of that? Only new-style optional packages should be automatically added to

Re: [sage-devel] Automatic test of optional packages+updates

CHomP gets used by Sage if the system detects its presence. And then it leads to doctest errors. On Sunday, June 14, 2015 at 4:15:14 AM UTC-7, Nathann Cohen wrote: Indeed, chomp is installed but not in the list of sage -t optional packages. Turn 'chomp' into a new-style package and

[sage-devel] Re: Links for method cross-references

On Sunday, June 14, 2015 at 12:02:31 PM UTC-7, Nathann Cohen wrote: At first sight nothing seems to be wrong. Could yoy try with the absolute path of the method (sage.mod1.mod2.Class.method_name) instead of only the method's name? You could also try to compile the doc with --warn-links,

[sage-devel] Re: Interfacing Kenzo with Sage?

On Saturday, June 13, 2015 at 12:34:33 PM UTC-7, Dima Pasechnik wrote: Is there interest in providing algorithms available in Kenzo ( https://www-fourier.ujf-grenoble.fr/~sergerar/Kenzo/) in Sage? Absolutely! John -- You received this message because you are subscribed to the Google

[sage-devel] Some doctests are not being run

I noticed the following in doctest/sources.py: There are 7 tests in sage/combinat/dyck_word.py that are not being run There are 4 tests in sage/combinat/finite_state_machine.py that are not being run There are 6 tests in sage/combinat/interval_posets.py that

[sage-support] Re: How to get Sage back from a colon?

Control-C will cancel the current command and return you to the sage: prompt. John On Tuesday, June 9, 2015 at 9:58:46 AM UTC-7, Craig E Larson wrote: Sometimes I forget a parenthesis, etc, and I get a colon input prompt. Double-enter won't escape the colon. Correcting the syntax also

Re: [sage-devel] Question about Free algebra

sage: list(X) [((1, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0, 0), 1)] It looks like the tuple is a concatenation of 6 (one for each factor of X) tuples of length 6 (one for each generator): (1,0,0,0,0,0), (0,1,0,0,0,0), etc.,

Re: [sage-support] Re: Make doc error

Earlier in the docbuilding, I see this: [combinat ] building [inventory]: targets for 2 source files that are out of date [combinat ] updating environment: 0 added, 2 changed, 0 removed [combinat ] reading sources... [ 50%] sage/combinat/cluster_algebra_quiver/cluster_seed [combinat ] Encoding

[sage-devel] Re: [sage-support] Re: Make doc error

Earlier in the docbuilding, I see this: [combinat ] building [inventory]: targets for 2 source files that are out of date [combinat ] updating environment: 0 added, 2 changed, 0 removed [combinat ] reading sources... [ 50%] sage/combinat/cluster_algebra_quiver/cluster_seed [combinat ] Encoding

[sage-devel] Re: trouble with error message during doctest

, ... is a wild card and can match anything. A single dot would have to be matched exactly. John Thanks very much! On Tuesday, May 26, 2015 at 4:36:07 PM UTC-7, John H Palmieri wrote: On Tuesday, May 26, 2015 at 4:31:54 PM UTC-7, David Perkinson wrote: EXAMPLES:: sage: S

[sage-devel] Re: trouble with error message during doctest

This message apparently means Doctest contains explicit source line number. Can you provide an example of a doctest you changed when adding the deprecation warnings? John On Tuesday, May 26, 2015 at 4:11:36 PM UTC-7, David Perkinson wrote: Could someone help me with the following error

[sage-devel] Re: trouble with error message during doctest

On Tuesday, May 26, 2015 at 4:31:54 PM UTC-7, David Perkinson wrote: EXAMPLES:: sage: S = sandpiles.Complete(4) sage: D = SandpileDivisor(S, {0: 0, 1: 0, 2: 8, 3: 0}) sage: E = SandpileDivisor(S, {0: 2, 1: 2, 2: 2, 3: 2}) sage: v = firing_vector(S, D, E)

[sage-devel] Re: Why \wedge works but \vee does not?

For me, it works using a raw string: title=r$A \wedge B=1$ and $A \vee B=0$. Have you tried that? (I don't know if it's a bug: I think it's always safer to use raw strings when the strings contain backslashes.) John On Monday, May 25, 2015 at 1:48:30 AM UTC-7, Jori Mäntysalo wrote:

[sage-support] Re: installing optional packages

On Tuesday, May 19, 2015 at 2:14:59 AM UTC-7, Emmanuel Charpentier wrote: Something is definitely out of joint in packages management. Thanks to the current migration of sagemath.org, I rebuilt from scratch (= from the tarball) sage 6.7 on a slow machine. The resultant system :

[sage-release] Re: Sage 6.7 released

On Tuesday, May 19, 2015 at 1:13:34 PM UTC-7, John H Palmieri wrote: On Sunday, May 17, 2015 at 4:28:45 PM UTC-7, Volker Braun wrote: The master and develop branch both have been updated to the 6.7 release! The self-contained binary tarball is on its way to the mirrors. I downloaded

[sage-release] Re: Sage 6.7 released

On Sunday, May 17, 2015 at 4:28:45 PM UTC-7, Volker Braun wrote: The master and develop branch both have been updated to the 6.7 release! The self-contained binary tarball is on its way to the mirrors. I downloaded the tarball and tried to build from scratch. With

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

On Thursday, May 14, 2015 at 10:09:11 AM UTC-7, leif wrote: William Stein wrote: Hi, I built sage-6.7.beta4 fine, then did git pull, then build sage-6.7.beta5 fine, which passed all tests. But I can't do ./sage -bdist ...: sage -t --long --warn-long 64.2

Re: [sage-support] Re: Is there anywhere I can download the entire Sage documentation in HTML (ZIP) or PDF format?

Try opening the file SAGE_ROOT/src/doc/output/html/en/index.html in your web browser (where SAGE_ROOT is the top directory in your Sage installation). Is that something like what you want? Note that if you've built the pdf documentation (by running make doc-pdf, for example) then there

[sage-devel] Re: Poll: Supplemental graphical visualizations

[X] Yes, I want graphical user interfaces that make use of the graphical abilities On Monday, May 4, 2015 at 11:32:53 AM UTC-7, Nathann Cohen wrote: Helloo, and any other representation of a graph is rather uninstructive Err... Well. Try graphs.RandomGNP(30,.5).show() to get an

[sage-support] Re: Differential graded algebras with homological indexing

On Friday, May 1, 2015 at 3:04:45 AM UTC-7, John Wiltshire-Gordon wrote: According to the documentation for commutative_dga, a differential graded algebra is graded by integers. However, if I attempt to give a generator negative degree, I get an error. For example, A =

Re: [sage-devel] Why packages tarballs have to be in lowercase ?

On Thursday, April 30, 2015 at 2:43:43 AM UTC-7, Jeroen Demeyer wrote: On 2015-04-30 08:57, Emmanuel Charpentier wrote: The Developer's guide http://www.sagemath.org/doc/developer/packaging.html#directory-structure states the ported packages' tarballs have to be in *lower case* :

[sage-devel] Re: xcode 6.3

On Sunday, April 26, 2015 at 3:53:08 PM UTC-7, Dima Pasechnik wrote: On Sunday, 26 April 2015 23:43:28 UTC+1, Dima Pasechnik wrote: On Sunday, 26 April 2015 23:21:22 UTC+1, Dima Pasechnik wrote: xcode 6.3.1 is out, and seems to be working better, at least I don't see silly errors (I

Re: [sage-devel] sage always executes the binary found in SAGE_ROOT

As far as I can tell, it is never a good idea to set SAGE_ROOT, nor is it ever suggested that you do so in the documentation. I think you could expect things to break if you set environment variables which Sage uses internally. One solution is to create a link '/usr/local/bin/sage' pointing to

[sage-combinat-devel] Categories and the top level

I've been wondering lately about the design choice of having all of the various categories accessible at the top-level in Sage. Would it be preferable to have a catalog of categories accessible via categories.AdditiveMagmas(), etc.? Having more than 50 categories could be viewed as polluting

[sage-devel] Re: xcode 6.3

On Friday, April 10, 2015 at 8:11:29 AM UTC-7, Volker Braun wrote: Just installed the new xcode command line tools (6.3) and it seems that the C++ compiler is totally hosed: It seems like this sort of thing happens not infrequently with Apple. I recall upgrading Xcode in the past and having

[sage-support] Re: How do I backup my notebook files? The SAGE notebook will not open...

On Monday, April 6, 2015 at 12:53:45 PM UTC-7, manrique.m...@gmail.com wrote: Actually, maybe I am misunderstanding something... I get this when I try to retrieve my notebook files: user@debian:~$ cd /.sage/sage_notebook.sagenb/home/admin/ bash: cd:

[sage-support] Re: Whats wrong with my function syntax?

If I copy and paste your code, I also get an error. The reason is that the first symbol you use for subtraction is not a hyphen, but some other symbol which looks very much like a hyphen, but which Sage does not recognize. (The second subtraction symbol seems to be okay.) Try using hyphens

[sage-devel] Re: Missing _sqlite3 when compiling conway polynomials OSX 10.9.5

On Tuesday, March 31, 2015 at 11:31:42 AM UTC-7, David Einstein wrote: The sqlite package seems to have installed correctly. Log attached. On OS X, Sage's sqlite package just creates a link to the pre-existing file /usr/bin/sqlite3. The error mentioned _sqlite3, which is a Python module

[sage-devel] Re: Missing _sqlite3 when compiling conway polynomials OSX 10.9.5

and see what happens. Thanks for the help. On Tuesday, March 31, 2015 at 2:50:38 PM UTC-4, John H Palmieri wrote: On Tuesday, March 31, 2015 at 11:31:42 AM UTC-7, David Einstein wrote: The sqlite package seems to have installed correctly. Log attached. On OS X, Sage's sqlite package

[sage-support] running a .spyx file?

Did running a .spyx file break? If I have a file testing.spyx' containing import sage.all sage.all.ZZ and then I run 'sage testing.spyx', I get an error: AttributeError: 'module' object has no attribute 'all' I think this ought to work. Should 'from sage.all import *' work also? It

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

On Friday, March 20, 2015 at 8:39:29 AM UTC-7, kcrisman wrote: Upgrading from previous beta: Processing dependencies for sagenb==0.11.4 Finished processing dependencies for sagenb==0.11.4 ln: ./: File exists real2m9.507s user0m26.172s sys 0m10.378s

[sage-devel] Re: cartesian_product

On Friday, March 6, 2015 at 3:12:40 PM UTC-8, Volker Braun wrote: On Friday, March 6, 2015 at 10:46:23 PM UTC+1, John H Palmieri wrote: sage: C = cartesian_product([FiniteEnumeratedSet([1,2,3]), FiniteEnumeratedSet([1,2,3])]) Though at that point sage: [(i,j) for i in range(3

[sage-devel] Re: cartesian_product

On Friday, March 6, 2015 at 1:35:12 PM UTC-8, Travis Scrimshaw wrote: The lower-case version is meant to be a functorial construction and IIRC eventually replace the CamelCase version. The closest thing to getting it to work currently is: sage: C = cartesian_product([Set([1,2,3]),

[sage-release] Re: Sage 6.5.rc3 released

On Friday, February 13, 2015 at 3:24:17 AM UTC-8, Volker Braun wrote: Hot on the heels of rc2, this should fix the remaining OSX testsuite failure All tests passed for me on OS X. -- John -- You received this message because you are subscribed to the Google Groups sage-release group. To

<    5   6   7   8   9   10   11   12   13   14   >