[sage-devel] Re: tab-completion in sage_mode / emacs broken

I'm sorry, I should have mentioned that I tried both sage_mode 0.10 and https://bitbucket.org/gol/sage-mode/downloads/sage_mode-20140407.spkg without success. In case it is of any help: I tried the %psearch within sage, whi

Re: [sage-devel] Re: tab-completion in sage_mode / emacs broken

Hi Ivan! thanks for your rapid reply! I only got to the problematic computer today. So: %colors NoColor > works (which is wonderful!), but https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-0.11.spkg doesn't :-( Martin -- You received this message because you are subscribed to the

[sage-devel] Re: redesign combinatorial statistics

OK, great, thanks for clarifying! Am Mittwoch, 28. Mai 2014 20:53:36 UTC+2 schrieb Simon King: > > Hi Martin, > > On 2014-05-28, 'Martin R' via sage-combinat-devel < > sage-comb...@googlegroups.com > wrote: > >> E.g., it should know domain and codomain, and it should know > >> what category it

[sage-devel] Re: redesign combinatorial statistics

> > E.g., it should know domain and codomain, and it should know > what category it belongs to. I think it makes sense to let a morphism > know whether it is injective or surjective. However, additional > information that is certainly interesting to researchers (e.g.: "Was first > defined by J

Re: [sage-devel] tab-completion in sage_mode / emacs broken

> Ack! Sorry I didn’t reply to you earlier. Needless to say it’s working for me. I wonder if you have an old version hanging around. I presume you restarted Emacs? What are the values of `sage-mode-version’ and `sage-startup-before-prompt-command’? If you customized the latter, you will h

[sage-devel] Re: #16577: enable 0-based row/column permutation of matrices

Hi there! Do I understand correctly, that this patch only concerns how permutations act on matrices, and that this is defined in the matrix class? If so, I think that I wouldn't expect "standard permutations" (i.e., permutations of 1,...,n) to work - unless of course there is a matrix class wi

[sage-devel] Re: #16577: enable 0-based row/column permutation of matrices

> > The ticket only adds a new feature allowing for the natural 0-based > permutations. Otherwise it does not change the current behavior. But why shouldn't the current behaviour be deprecated? I think requiring that the domain is 0..n-1 (is possible, with a check) would be much better. Mart

Re: [sage-devel] Re: #16577: enable 0-based row/column permutation of matrices

Am Mittwoch, 10. September 2014 19:54:06 UTC+2 schrieb Nils Bruin: > > On Wednesday, September 10, 2014 10:38:50 AM UTC-7, Nils Bruin wrote: >> >> sage: Permutation([0,1,2]) >> > > aw shoot. The problem is there already, because we're defining > permutations by *ordered list of images* rather than

Re: [sage-devel] Re: #16577: enable 0-based row/column permutation of matrices

Am Mittwoch, 10. September 2014 21:03:36 UTC+2 schrieb Nils Bruin: > > On Wednesday, September 10, 2014 11:51:55 AM UTC-7, Martin R wrote: >> >> I think that's what PermutationGroup and PermutationGroupElement do. > > No: > > sage: PermutationGroupElement((2,3,4)).parent() > Symmetric group of orde

Re: [sage-devel] Re: #16577: enable 0-based row/column permutation of matrices

Am Donnerstag, 11. September 2014 01:36:40 UTC+2 schrieb Nils Bruin: > > On Wednesday, September 10, 2014 10:54:06 AM UTC-7, Nils Bruin wrote: >> >> On Wednesday, September 10, 2014 10:38:50 AM UTC-7, Nils Bruin wrote: >>> >>> sage: Permutation([0,1,2]) >>> >> > In fact, one CAN see from this lis

Re: [sage-devel] Re: Poset/lattice, join and join_matrix

Am Donnerstag, 23. Oktober 2014 11:11:34 UTC+2 schrieb Jori Mantysalo: > > On Thu, 23 Oct 2014, Nathann Cohen wrote: > > >> Ok. To have join(a,b,c,...) or join([a,b,c,...])? > > > > Hmmm.. Well, we can have both at the same time. > > True, but is it good for user perspective to have two ways to

Re: [sage-devel] Re: Code of Conduct

Am Samstag, 22. November 2014 16:48:09 UTC+1 schrieb Nicolas M. Thiéry: Conclusion: > [...] Of course, nothing beats leading by example. > > Given that a formal Code of Conduct seems to make uncomfortable some > developers for whom I have a strong respect, I am not anymore in favor > of

Re: [sage-devel] Oneliners

I'm trying to get a more precise notion of "one-liner" and understand better which one-liners should not be in the library. At first I thought it might be: "a function which is a composition of at most two 'user space' functions" but as Nathann just wrote, this is not correct for P.is_connecte

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

e know if that solves the issue. If so, then maybe we can add a > workaround to sage-mode or figure out how to get ipython to stop sending > the control sequences. If not it would be helpful to know what version of > Emacs you’re running. > > -Ivan > > On Aug 11, 2016, at 3:49

[sage-devel] fricas interface

There is a new FriCAS interface almost ready for review at https://trac.sagemath.org/ticket/21231. Comments and help very welcome. I would especially like to encourage those who use FriCAS in their real life to tell me at the ticket which bits they use, so I can make sure the translation from

[sage-devel] __repr__ in sage.interfaces.InterfaceElement called twice

While working on the new fricas interface, I noticed that the method __repr__ in sage.interfaces.InterfaceElement is always called twice. Apparently, once by __call__ in fancy_repr.py, and a second time by _repr_pprint in pretty.py. Is this intentional? The problem is that in the interface wo

[sage-devel] fricas interface ready for review

https://trac.sagemath.org/ticket/21231 -- 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 t

[sage-devel] Re: __repr__ in sage.interfaces.InterfaceElement called twice

now building... Am Mittwoch, 17. August 2016 20:38:12 UTC+2 schrieb Volker Braun: > > I made https://trac.sagemath.org/ticket/21269 > > > > On Wednesday, August 17, 2016 at 10:04:47 AM UTC+2, Martin R wrote: >> >> While working on the new fricas interface, I noticed that the >> method __repr__ in

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Since solving this appears to be tricky, is there a way to undo the ipython-5 thing? (I'd like to keep other things from sage 7.4... -- 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

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Am Donnerstag, 18. August 2016 13:33:41 UTC+2 schrieb Volker Braun: > > PS: It would be easy enough to expose the simple-prompt either to the sage > command line or have a special sage-embedded commandline entrypoint that > starts witout any ANSI sequences. > > I have absolutely no idea how to

[sage-devel] please review #21231 (interface to fricas)

I spent a few hours yesterday to rebase and polish the new fricas interface. It would be great if somebody could re-review it. I should mention that there are three remaining issues: 1) there are three non-doctested methods, where I have no idea how to doctest them, but they make the patchbot

Re: [sage-devel] Getting rid of reset() and restore()?

I use it all the time, mainly for "x", "n", and "pi": sage: n = 5 sage: del n sage: n --- NameError Traceback (most recent call last) in () > 1 n NameError: name 'n' is not defined sage: r

Re: [sage-devel] Getting rid of reset() and restore()?

right. Am Montag, 19. September 2016 15:58:25 UTC+2 schrieb Jeroen Demeyer: > > On 2016-09-19 15:55, 'Martin R' via sage-devel wrote: > > I use it all the time, mainly for "x", "n", and "pi": > > But never reset() without arguments? &

[sage-devel] Re: Blocker tickets needs review

I think that the emacs ticket should not be a blocker anymore. stakemori did a great job! Martin Am Dienstag, 20. September 2016 15:19:20 UTC+2 schrieb Jeroen Demeyer: > > Hello, this is a reminder that currently 3 blocker tickets need review. > All of them have some discussion, but they all s

[sage-devel] Re: Sage's references: new policy?

Why not use the MR number as reference format? Martin Am Mittwoch, 21. September 2016 01:03:27 UTC+2 schrieb John H Palmieri: > > As discussed in another thread [1]_ on sage-devel recently, I propose > changing our policy toward references: > > - all references should be put into a master biblio

Re: [sage-devel] Re: Sage's references: new policy?

rences, i.e. > make [Bla]_ and [Foo]_ both refer to [Foo]. > This would allow less changes in the source. > > > > >> David >> >> On Wed, Sep 21, 2016 at 4:38 AM, 'Martin R' via sage-devel < >> sage-...@googlegroups.com> wrote: >>

Re: [sage-devel] Re: Sage's references: new policy?

Am Mittwoch, 21. September 2016 13:36:31 UTC+2 schrieb Dima Pasechnik: > > > > On Wednesday, September 21, 2016 at 9:36:06 AM UTC, Martin R wrote: >> >> well, for preprints clearly there is of course the arXiv number and for >> sciences without a good database, there is doi. >> >> concerning reada

Re: [sage-devel] Re: Sage's references: new policy?

Am Mittwoch, 21. September 2016 13:49:57 UTC+2 schrieb Johan S. R. Nielsen: > > With MR numbers, do you mean a link of the type [MR3352496]? > Yes! (Except, that in a compiled document such links could be transformed into a link such as [1]. > > well, for preprints clearly there is of cours

Re: [sage-devel] Re: openblas segfault?

On my computer, 7.4.beta6 doesn't seem to compile openblas successfully either. After make distclean and make I get an error (log attached). real 135m22.614s user 407m51.656s sys 21m22.276s *** Error building Sage. The following packag

Re: [sage-devel] Re: openblas segfault?

I forgot: martin@Martin-Laptop:~/sage-develop$ lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):4 On-line CPU(s) list: 0-3 Thread(s) pro Kern:1 Kern(e) pro Socket:4 Socket(s): 1 NUMA-Knoten:

Re: [sage-devel] Re: openblas segfault?

I just tried make after saying "export TARGET=P2". Doing so, openblas starts to build but fails after a while saying ar: sgemm_kernel.o: No such file or directory ../Makefile.tail:40: recipe for target 'libs' failed make[4]: *** [libs] Error 1 make[4]: Leaving directory '/home/martin/sage-devel

Re: [sage-devel] Re: openblas segfault?

Thanks, now (and for the next few hours :-) trying... Am Montag, 26. September 2016 21:06:17 UTC+2 schrieb Michael Orlitzky: > > On 09/26/2016 03:03 PM, 'Martin R' via sage-devel wrote: > > > > Is there a quick fix? > > > > To get something usable,

Re: [sage-devel] About exceptions

wouldn't it make sense to catch "everything reasonable"? I could imagine that for some reason at some point it is decided that the method you call raises a slightly different error. Would that be bad? Martin -- You received this message because you are subscribed to the Google Groups "sage

[sage-devel] git-trac push

git-trac doesn't like me - what have I done wrong? martin@Martin-Laptop:~/sage-develop$ git-trac push 21594 Pushing to Trac #21594... Guessed remote branch: u/mantepse/growth_diagrams Traceback (most recent call last): File "/home/martin/git-trac-command/bin/git-trac", line 18, in cmdline.l

[sage-devel] Re: git-trac push

no idea why, but now it works (I deleted the branch and checked it out again :-) Martin Am Dienstag, 18. Oktober 2016 08:56:21 UTC+2 schrieb Martin R: > > git-trac doesn't like me - what have I done wrong? > > martin@Martin-Laptop:~/sage-develop$ git-trac push 21594 > Pushing to Trac #21594... >

[sage-devel] sphinx, texinfo and emacs

As you may know, using https://github.com/sagemath/sage-shell-mode, working with sage in emacs is a very enjoyable pastime. In particular, typing at the sage prompt sage: sage.combinat.posets? opens a new frame and displays the documentation of sage.combinat.posets there. However, to my dismay

Re: [sage-devel] sphinx, texinfo and emacs

at-posets > > > At least, on my machine it prints the exact same information. > > Best, > Johan > > 'Martin R' via sage-devel writes: > > > As you may know, using https://github.com/sagemath/sage-shell-mode, > working > > with sage in emacs is a

[sage-devel] Re: sphinx, texinfo and emacs

as a first step to answering (2), I just applied the patch below, and it seems to build the reference in texinfo format. diff --git a/src/sage_setup/docbuild/__init__.py b/src/sage_setup/docbuild/__init__.py index 0bd52a6..9ddf7d4 100644 --- a/src/sage_setup/docbuild/__init__.py +++ b/src/sage_s

Re: [sage-devel] sphinx, texinfo and emacs

Am Donnerstag, 20. Oktober 2016 13:05:59 UTC+2 schrieb Johan S. R. Nielsen: > > > Yes, but there are no links. Or do you have them? > > True, they are not links. It would be nice if they were, though > personally I like that what is printed is the actual module name that I > should type in foll

[sage-devel] Re: sphinx, texinfo and emacs

after patching and doing ./sage -docbuild reference texinfo I get many *.texi files, and in each directory a makefile. After installing makeinfo (sudo apt-get install info), and doing make, I get very nice looking info files, and at least the top one seems to work very well. Even in the unlike

[sage-devel] Re: sphinx, texinfo and emacs

this is now https://trac.sagemath.org/ticket/21734 help is much appreciated -- 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.co

[sage-devel] Re: sphinx, texinfo and emacs

Eli Zaretskii from the texinfo team helped me with two problems I had, and texinfo documentation is now almost ready to go. I need help with three things, which I report here, because trac is down. 1.) for some reason, it is necessary that makeinfo is called with "--footnote-style separate". H

[sage-devel] Re: sphinx, texinfo and emacs

Am Freitag, 21. Oktober 2016 22:18:48 UTC+2 schrieb John H Palmieri: > > > > On Friday, October 21, 2016 at 12:31:01 PM UTC-7, Martin R wrote: >> >> Eli Zaretskii from the texinfo team helped me with two problems I had, >> and texinfo documentation is now almost ready to go. I need help with >

[sage-devel] Re: sphinx, texinfo and emacs

Am Freitag, 21. Oktober 2016 23:51:18 UTC+2 schrieb Matthias Koeppe: > > > We already have makeinfo as part of the autotools package. > great! one further question: I noticed that there may also be other files such as pictures (in .png) format which "sage -docbuild DOCUMENT texinfo" puts into

[sage-devel] Re: sphinx, texinfo and emacs

I guess you need more than the filename, you also need the info node, no? Martin -- 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...@googlegrou

[sage-devel] Re: sphinx, texinfo and emacs

apparently the name sagereferencemanualstandardcommutativerings.info is autogenerated by sphinx and could be customized somehow, just I do not know how yet. See http://www.sphinx-doc.org/en/1.4.8/config.html (options for texinfo output). Martin Am Samstag, 22. Oktober 2016 13:52:13 UTC+2 schr

[sage-devel] Re: sphinx, texinfo and emacs

the key is what gets written into conf.py by class SingleFileBuilder(DocBuilder) from docbuild/__init__py. what would be a good naming scheme for the files? I assume something like the name of the python source directory, right? Martin Am Samstag, 22. Oktober 2016 17:42:42 UTC+2 schrieb Marti

[sage-devel] Re: Multivariate polynomial factoring and bug(?)

FriCAS does this in no time: sage: R. = PolynomialRing(QQ) sage: f = z^40*y^6*x^2100 + 2*t^15*z^53*y^9*x^2078 + z^40*y^7*x^2003 + z^40*y^6*x^2000 - 14*z^31*y^6*x^1102 - 2*t*z^20*y^3*x^1101 + 78*z^20*y^3*x^1100 - 28*t^15*z^44*y^9*x^1080 - 4*t^16*z^33 : *y^6*x^1079 + 156*t^15*z^33*y^6*x^1078

[sage-devel] Re: Multivariate polynomial factoring and bug(?)

Actually, I didn't even know that I changed the variable (because the fricas interface treats all these as POLY INT). So I did a test in fricas, and indeed, the bad ordering seems to be with y as first variable. Having t first takes no time even on my (old) laptop, having z first takes a seco

Re: [sage-devel] RFC: correct way to deal with particular methods

I have a possibly related question on documentation. At https://trac.sagemath.org/ticket/21594 I have an class GrowthDiagram, which is not intended for the end user. Instead, there are several subclasses (GrowthDiagramRSK, GrowthDiagramBinWord, GrowthDiagramDomino, etc.), which, however, all

Re: [sage-devel] RFC: correct way to deal with particular methods

hods which are overwritten are not taken from the parent class. Martin Am Montag, 7. November 2016 16:04:07 UTC+1 schrieb Travis Scrimshaw: > > > > On Monday, November 7, 2016 at 7:26:57 AM UTC-6, Jeroen Demeyer wrote: >> >> On 2016-11-07 14:13, 'Martin R' via s

Re: [sage-devel] RFC: correct way to deal with particular methods

That's actually precisely what I'd like. So, what are metaclass conflicts? Martin Am Dienstag, 8. November 2016 12:37:20 UTC+1 schrieb Erik Bray: > > On Tue, Nov 8, 2016 at 8:58 AM, 'Martin R' via sage-devel > > wrote: > > Thanks for these hints! I

[sage-devel] Re: Hermite normal form of matrix over polynomial ring

An optimised version is implemented in fricas, available as fricas. HP_solve It might provide a good benchmark. Martin -- 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 ema

[sage-devel] Re: Recurrences and Sequence Formula Guessing Functions in Sage

I'd be interested in what output you'd like to have. The hard part in the FriCAS package was to get decent speed, changing output should be relatively straightforward. (I guess that you are aware of the possibility of using the package from within sage) Martin Am Samstag, 19. November 2016 16

[sage-devel] Re: Recurrences and Sequence Formula Guessing Functions in Sage

out off the box, the FriCAS package can do the following (described in some detail in https://arxiv.org/abs/math/0702086, the journal published a shortened version): 1) Generating functions: * rational (guessPade) * algebraic (guessAlg) * linear diffeq (guessHolo) * polynomial diffeq (guessADE)

[sage-devel] Re: Recurrences and Sequence Formula Guessing Functions in Sage

I forgot to add: once a diffeq for a generating function is found, the package can also give you the 1783-th coefficient of the generating function. And, most importantly: the main thing to do to make it really useful for sage, is to implement a better conversion from sage lists to fricas lists

Re: [sage-devel] Re: Recurrences and Sequence Formula Guessing Functions in Sage

Am Samstag, 19. November 2016 21:23:10 UTC+1 schrieb Maxie Schmidt: > > Thanks for all of the suggestions. I think I will start by getting all of > Martin's package routines working under a single wrapper function and try > to improve from there. > I think that one question is how you want to r

[sage-devel] Re: Recurrences and Sequence Formula Guessing Functions in Sage

Did anybody ever compare the possibilities speed-wise? The scope of these packages is quite different: ore_algebra is for the holonomic and q-holonomic universe, the guessing facility in fricas is for guessing only - but covers also polynomial recurrences and differential equations (and their q

[sage-devel] Re: Recurrences and Sequence Formula Guessing Functions in Sage

> > 2.As to guessing holonomic recurrences there is the Ore algebra package. > It would be nice to have a tutorial. > what's wrong with https://arxiv.org/abs/1306.4263 ? Martin -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fr

[sage-devel] Re: Error building openblas-0.2.19

You will probably need a variation of the following: https://groups.google.com/d/msg/sage-release/3QJoAgg9bgo/5uvnTLV1AwAJ Martin -- 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, s

[sage-devel] Re: Blog post "Sphinx documentation of Cython code using ``binding=True``"

Does this mean that eventually a solution to the texinfo crossreferencing problem in https://trac.sagemath.org/ticket/21734 could be found? (essentially, the problem was, if I remember correctly, that the way sphinx for sage is set up, sage is not a single project. Instead, we have many "exter

[sage-devel] Re: [sage-release] Sage 8.0.beta12 released

I'm afraid I stumbled across something potentially dangerous: https://trac.sagemath.org/ticket/23317 Martin -- 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-

[sage-devel] Surprising behaviour of Set

I just noticed that Set([[], []]).cardinality() yields 2. In earlier versions, a TypeError: unhashable type: 'list' was raised. I think the behaviour was modified in https://trac.sagemath.org/ticket/22597. Is this intended? It seems to me that it would be safer if cardinality would raise an

Re: [sage-devel] Surprising behaviour of Set

This is now https://trac.sagemath.org/ticket/23324 Am Sonntag, 25. Juni 2017 19:47:36 UTC+2 schrieb vdelecroix: > > On 25/06/2017 19:10, 'Martin R' via sage-devel wrote: > > I just noticed that Set([[], []]).cardinality() yields 2. In earlier > > versions, a TypeE

[sage-devel] Plotting of digraphs with multiple edges

I am not sure whether this is a bug, in any case I'd need a workaround. Consider (with dot2tex installed) D = DiGraph([(0, 1, 0), (1, 2, 0), (2, 3, 0), (2, 4, 0)], multiedges=True); D.plot(layout="acyclic") E = DiGraph([(0, 1, 0), (1, 2, 0), (2, 3, 0), (2, 4, 0), (2, 4, 1)], multiedges=True);

[sage-devel] Re: Plotting of digraphs with multiple edges

It might be helpful to know where in GraphPlot the layout engine is chosen, and which one corresponds to which picture. I think I understand that it depends on GraphPlot._arcs and GraphPlot._arcdigraph. However, I cannot find out why the first graph D gets pinkish vertices, and the second grap

Re: [sage-devel] About SetPartition.to_permutation

Am Donnerstag, 17. Dezember 2015 14:12:06 UTC+1 schrieb Nathann Cohen: > > > If you have an *ordered set* there is a canonical way to define one > > permutation from a partition. You make it so that the atom of the > partitions > > are your cycles. > > Yeah, sort everything. Wonder when somet

Re: [sage-devel] About SetPartition.to_permutation

Actually, I propose to delete all code from sage, because it doesn't work in all circumstances. It might be useful for some people (not all that many), but we are actually doing them a favour because we save them from using software in circumstances where it doesn't apply. Thus, by deleting sa

Re: [sage-devel] About SetPartition.to_permutation

Am Freitag, 18. Dezember 2015 09:39:57 UTC+1 schrieb Dima Pasechnik: > > > > On Friday, 18 December 2015 08:33:05 UTC, Martin R wrote: >> >> Actually, I propose to delete all code from sage, because it doesn't work >> in all circumstances. >> >> It might be useful for some people (not all that m

Re: [sage-devel] About SetPartition.to_permutation

I tried to point out a possible improvement to the SetPartition code in http://trac.sagemath.org/ticket/19737, because I used this code. I also provided a patch. I was told that the original code is nonsensical. I disagree. In fact, from a recent experience with sage now disallowing empty ro

[sage-devel] UniqueRepresentation in FormalSums

Hi there! I'm trying to understand inheritance. In formal_sum I find the following code: class FormalSums(UniqueRepresentation, Module): Element = FormalSum def _element_constructor_(self, x, check=True, reduce=True): if isinstance(x, FormalSum): P = x.parent()

Re: [sage-devel] UniqueRepresentation in FormalSums

> > 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” evaluates to “True” if the > objects ‘a’ and ‘b’ *are the same” (i.e., ar

Re: [sage-devel] UniqueRepresentation in FormalSums

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 understand the difference between ‘is’ and ‘==‘ may require some >>> background in programming. >>> >>> Specifically, “a==b” evaluates to “Tr

[sage-devel] Re: UniqueRepresentation in FormalSums

This is now #19886. -- 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 thi

Re: [sage-devel] Docstring-wide "# optional" markup (#20427) / I am grumpy

A thought: it might in fact be a feature that tab completion *does* show methods which only work with optional packages. I usually try tab-completion first. I won't mind at all hitting an error message "Please install the optional package Foo" if it saves me an hour of internet search, fiddli

Re: [sage-devel] Docstring-wide "# optional" markup (#20427) / I am grumpy

That would be awesome! In fact, within emacs (sage-mode) I also get all the underscored methods, which I don't like at all. I should ask about that... Am Mittwoch, 13. April 2016 23:12:37 UTC+2 schrieb mmarco: > > That's a valid point. Maybe there is a middle option that could combine > the b

Re: [sage-devel] Re: Tab completion on results of method calls

I am using emacs/sage-mode only, so my experience is biased. What I would like though is that tab completion automatically adds at least the open parenthesis, or possibly both, whenever appropriate. Would this make sense and would this be possible? Perhaps one could do even more - I don't know

[sage-devel] copying MixedIntegerLinearProgram problem

Hi there! I am having a severe problem with a program of mine that stopped working, very likely after upgrading to 7.2.beta5, but I'm afraid I don't know from which version. (I believe something after 7.1) The error I get is: ValueError: Variable MIPVariable of dimension 1 is a variable from

Re: [sage-devel] copying MixedIntegerLinearProgram problem

So, what is the proper way to do it? As I wrote, it's not really an option to solve the whole problem for each new constraint... Martin -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails fro

Re: [sage-devel] copying MixedIntegerLinearProgram problem

> So, what is the proper way to do it? As I wrote, it's not really an >> option to solve the whole problem for each new constraint... >> > > add a constraint, and solve again? > > Yes, and then? I don't think I can remove it again, can I? As I wrote, pseudo-code is as follows, and keep in mi

Re: [sage-devel] copying MixedIntegerLinearProgram problem

Yes, and then? I don't think I can remove it again, can I? > > sage: p.remove_constraint? > Docstring: >Removes a constraint from self. > > I do not thing that this works, because a constraint may (and often will be) subsumed by other constraints already there. -- You received this mes

Re: [sage-devel] copying MixedIntegerLinearProgram problem

remove_constraint takes as input the index of the constraint to be removed! It is unlikely, that add_constraint(variable==0) creates an indexed constraint, but perhaps I am mistaken. Am Freitag, 13. Mai 2016 15:25:17 UTC+2 schrieb Dima Pasechnik: > > On Friday, May 13, 2016 at 9:53:13 AM UTC+1,

Re: [sage-devel] copying MixedIntegerLinearProgram problem

Dear Dima! Thank you for your interest! (I was away for the weekend...) remove_constraint takes as input the index of the constraint to be >> removed! It is unlikely, that add_constraint(variable==0) creates an >> indexed constraint, but perhaps I am mistaken. >> > > Somewhat naively, I'd

Re: [sage-devel] Users can permanently modify GF(5).list()

A suggestion for a behaviour of "x.list()": as a user I'd hope for sage: x = C.random_element(); p = x.list(); C(p) == x True Martin -- 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

[sage-devel] Trouble compiling develop

I am having trouble making sage. Am I missing something obvious? Martin make[1]: Verzeichnis »/home/martin/sage-master/build/make« wird betreten make base make[2]: Verzeichnis »/home/martin/sage-master/build/make« wird betreten sage-logger -p 'sage-spkg patch-2.7.5' '/home/martin/sage-master

[sage-devel] Re: FriCAS installation fails

Are http://www.sagemath.org/git-developer-guide/packaging.html the instructions I should follow? Martin Am Mittwoch, 10. August 2016 18:55:55 UTC+2 schrieb Dima Pasechnik: > > Also, we have an old version of FriCAS, current is 1.2.7. > I just opened > > https://trac.sagemath.org/ticket/21209 (u

[sage-devel] Re: FriCAS installation fails

I get :~$ sage --package create fricas --version 1.2.7 --tarball fricas-1.2.7.tar.bz2 --type experimental ERROR [cmdline|run:74]: unknown subcommand: create with ┌┐ │ SageMath version 7.3.beta4, Release Date: 2016-06-12

[sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Please Help! I just installed develop, which is currently sage 7.4 beta0, but this broke my beloved sage_mode. All in and output except the banner is unreadable! I cannot live (well, to be honest: work) without emacs and sage_mode :-( Martin ┌─

[sage-devel] Re: sage_mode for emacs has display problem in sage 7.4 beta0

This is now https://trac.sagemath.org/ticket/21227 -- 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

[sage-devel] performance issue with initialization of trees

Dear all, I'm having a performance problem, and I believe I have successfully located it in the initialization code of LabelledBinaryTrees. Part of my code is simply computing the binary tree corresponding to a permutation. I have the following timing: sage: timeit("[pi.binary_search_tree()

[sage-devel] Re: performance issue with initialization of trees

Great! I created #23821 to collect improvements! Martin Am Sonntag, 10. September 2017 08:19:02 UTC+2 schrieb Travis Scrimshaw: > > Hey Martin, >I am also getting similar timings, but actually testing Permutations(7) > both times. :P What is more interesting is %prun: > > sage: %prun L = [p

[sage-devel] performance issue with poset constructor

Dear all! I need some guidance with yet another initializer, this time posets. The ticket is https://trac.sagemath.org/ticket/23825, the crucial issue is that, to create a poset, it seems that we first create a digraph corresponding to the data, then turn this digraph into a Hasse diagram, and

[sage-devel] sage-python puzzle

I don't understand the following timings: sage: A = AlternatingSignMatrices(6) sage: lC = [a.corner_sum_matrix() for a in A] sage: timeit("[from_corner_sum_1(corner) for corner in lC]", number=1, repeat=1) 1 loops, best of 1: 63 s per loop sage: timeit("[from_corner_sum_2(corner) for corner in lC

[sage-devel] Re: sage-python puzzle

Apparently, corner[i,j] is a lot faster than corner[i][j]. With this modification, the two versions are roughly equally fast. I don't get it, though, because the second version should be doing a lot more work. Martin Am Montag, 11. September 2017 16:23:07 UTC+2 schrieb Martin R: > > I don't u

[sage-devel] Re: sage-python puzzle

Thank you! Is there a recommended (fast) way to turn input into a (square) matrix (with entries in ZZ)? currently I do "corner = matrix(corner)" Thanks again, Martin Am Montag, 11. September 2017 17:00:20 UTC+2 schrieb Samuel Lelievre: > > Mon 2017-09-11, 9:38:45 (UTC-5), Martin R: > > Appa

[sage-devel] Re: [sagemath-admins] git trac connection problems from continental Europe

It worked for me after I rebooted my laptop (in Vienna, Austria). I guess it's a coincidence, but who knows... Martin Am Dienstag, 12. September 2017 13:26:03 UTC+2 schrieb Dima Pasechnik: > > I've created a trac mirror repo on github: > https://github.com/dimpase/sagetrac-mirror > Please pul

[sage-devel] Re: sage-python puzzle

Dear Samuel, almost by accident, I just noticed the following: def to_matrix_1(self): entries = { (v-1, i): 1 for i, v in enumerate(self) } return MatrixSpace(ZZ, len(self), sparse = True)(entries) def to_matrix_2(self): entries = { (v-1, i): 1 for i, v in enumerate(self) } retur

[sage-devel] Re: sage-python puzzle

Thanks for the hint. I am currently happy with %prun followed by %lprun. The only thing I dislike about this is that I have to guess who calls the most offending method or function, but it's not much of a hassle, since %prun also includes the cumulative timings. Martin Am Freitag, 15. Septem

[sage-devel] yet another sage-python performance puzzle

I am now trying to speed up Permutation.to_matrix, which is meanwhile one of the worst offenders in my application. After some profiling I found the following, which is quite a mystery to me. Apparently it is possible that importing a module in a method costs a significant amount of time! QUES

[sage-devel] Re: yet another sage-python performance puzzle

I haven't done any "professional" profiling, but it seems to me that the 10% are stable, i.e., roughly independent of the size of the permutation. I just found a much faster alternative: simply bypass MatrixSpace.matrix completely: entries = { (v-1, i): 1 for i, v in enumerate(self) }

  1   2   3   4   5   6   >