Re: [sage-devel] Should RR coerce into RIF?

). Therefore, my vote is On Tuesday, March 18 2014 16:22:44 UTC+1 Marco Streng wrote: 1) explicit conversion RR -- RIF: allow / disallow 2) explicit conversion RIF -- RR: allow / disallow 3) automatic coercisions: disallow / (RR--RIF) / (RIF--RR) 1) allow 2) disallow 3) disallow Best, Clemens Heuberger

[sage-devel] Documentation of assume in reference manual

The function sage.symbolic.assumptions.assume (and related functions) have documentation in their docstrings; however, the corresponding file src/sage/symbolic/assumptions.py is not contained in any .rst file for the reference manual. Therefore, the documentation of the function assume() does not

Re: [sage-devel] Re: Documentation of assume in reference manual

Am 2014-07-21 16:33, schrieb kcrisman: Note that src/sage/symbolic/assumptions.py would need some work in order to include it; at least, a ReSt title should be inserted. Is there a reason for this omission? Probably just an oversight at the time. Are you able/willing to

[sage-devel] Comparison between str and sage.rings.integer.Integer depends on whether doctest called directly or via Makefile

Can anyone help me understanding the following behaviour: A doctest (0 'I'; see below) passes when called directly and fails when called via a Makefile, reproduced under sage 6.3.beta6, 6.2, 5.10 (running Linux Mint). As pointed out in

[sage-devel] Re: Comparison between str and sage.rings.integer.Integer depends on whether doctest called directly or via Makefile

Am 2014-07-22 20:34, schrieb Nils Bruin: Would you be working on a 32-bit system by any chance? no, 64-bit system. Is the behaviour reproducible on other systems? Not on my 64 bit machine. May I ask on which system? This problem turned up when trying to find out why Volker

Re: [sage-devel] Re: Including private methods in documentation

, and the docstring of the __call__ method should provide a technical input specification and tests (e.g., of corner cases). Best regards, Simon -- Univ.-Prof. Dr. Clemens HeubergerAlpen-Adria-Universität Klagenfurt Institut für Mathematik, Universitätsstraße 65-67, 9020 Klagenfurt, Austria Tel

[sage-devel] Background documentation

In http://trac.sagemath.org/ticket/16782, I propose a patch implementing the Riemann Zeta function for complex intervals. For bounding the errors, I needed some rather boring estimates, in particular explicitly bounding errors in Taylor's theorem in my situation. These boring estimates now exist

[sage-devel] git trac log

I get (git-trac-command at 7e8fb34) $ git trac log 16538 Error: release manager has not merged Trac #16538 $ git trac log 16943 Error: release manager has not merged Trac #16943 $ git trac log 16786 Error: release manager has not merged Trac #16786 Actually, #16538 has been merged in 6.4.beta0,

[sage-devel] equal FractionFieldElement_1poly_field have different hashes

Up to now, my understanding was that if a == b, then hash(a) must be hash(b). However, this does not necessarily hold in the Fraction Field of Univariate Polynomial Ring in t over Rational Field, as the following example shows: sage: R.q = QQ[] sage: a = 1/q sage: b = 2/(2*q)

Re: [sage-devel] Re: equal FractionFieldElement_1poly_field have different hashes

Am 2014-09-18 um 18:12 schrieb Travis Scrimshaw: Hey, Things like this have popped up in a few places, where doing things in a fraction field over ZZ behaves much better than over QQ. I feel that anytime The same problem is in the Fraction Field of Univariate Polynomial Ring in u over

[sage-devel] Re: equal FractionFieldElement_1poly_field have different hashes

Am 2014-09-18 um 16:44 schrieb Stefan: Is this behaviour intentional or is this a bug? Neither, in Sage the Python promise is necessarily broken, because math objects and equality is just too complex. So how do I work with dict and set in sage? I ran across the difficulty in the

Re: [sage-devel] Re: equal FractionFieldElement_1poly_field have different hashes

Hi Simon, Am 2014-09-20 um 16:42 schrieb Simon King: On 2014-09-20, Clemens Heuberger clemens.heuber...@aau.at wrote: So how do I work with dict and set in sage? Carefully... That's to say, if your dictionary keys all live in the same ring (or other mathematical object) then it should

Re: [sage-devel] Re: equal FractionFieldElement_1poly_field have different hashes

Hi Simon, Am 2014-09-20 um 18:47 schrieb Simon King: On 2014-09-20, Clemens Heuberger clemens.heuber...@aau.at wrote: Shall I enforce that the parent of all labels is the same (and warn the user if this is not the case?). Probably, I'd also allow strings as an additional type because

[sage-devel] Failing doctests in sage/dev if $HOME/.sage is a symlink with trailing slash

My $HOME/.sage is a symbolic link with a trailing slash: ~ $ ls -ld .sage lrwxrwxrwx 1 cheuberg lsci 11 Sep 23 10:25 .sage - /tmp/.sage/ When running make ptestlong (sage 6.4.beta3) with this configuration, I get quite a number of failing doctests (see below for details) and several files are

[sage-devel] infinity norm of a sparse zero matrix

I accidentally encountered the following: sage: matrix([[0]], sparse=True).norm(oo) Traceback (most recent call last): ... TypeError: base_ring (=Category of objects) must be a ring The same for 1 and Frobenius norms. This happens in A = self.apply_map(abs).change_ring(RDF) What is the

[sage-devel] IntervalFieldElement and Sparse Linear Algebra

I'd like to use ComplexIntervalFieldElements in sparse vectors and matrices. Comparison of intervals is somewhat delicate ( for a real interval field element I: I != 0 holds iff 0 is not contained in I I == 0 holds iff I consists only of 0 bool(I) holds iff I does not

Re: [sage-devel] What should be the present working directory for sage -notebook=ipython ?

Am 2014-10-13 um 15:25 schrieb Sébastien Labbé: Note: With #16996, it is possible to start in the current directory with sage -notebook=ipython --notebook-dir=. Time to vote. What do you prefer as default directory for the ipython notebook? - pwd + 1 When I first read of

Re: [sage-devel] Re: What should be the present working directory for sage -notebook=ipython ?

Am 2014-10-13 um 17:30 schrieb Volker Braun: Also, if you vote yes then you volunteer for fixing the current notebook to match the behavior ;-) I do not think that this is necessary: one the one hand, it would lead to big deprecation; on the other hand, the current sage notebook with its user

[sage-devel] Optional Arb package (arbitrary-precision floating-point ball arithmetic)

In #16747, Karen Kohl and Laura Peskin proposed to include Fredrik Johansson's arb library as an optional package. I cleaned that up a little bit and set this to needs_review as I did not get any answers from the original authors. As it is, #16747 simply adds the library and does not do anything

Re: [sage-devel] SPKG Maintainers??

On 2014-10-29 09:32, Francois Bissey wrote: +1 On 29/10/2014, at 21:24, Jeroen Demeyer jdeme...@cage.ugent.be wrote: Hello, all SPKG.txt files list SPKG Maintainers. I never quite understood the reason for this. Mostly, this seems to have been added once when creating the SPKG and indeed

Re: [sage-devel] Bug in abs(I*x).diff(x)

-- Univ.-Prof. Dr. Clemens HeubergerAlpen-Adria-Universität Klagenfurt Institut für Mathematik, Universitätsstraße 65-67, 9020 Klagenfurt, Austria Tel: +43 463 2700 3121Fax: +43 463 2700 99 3121 clemens.heuber...@aau.athttp://wwwu.aau.at/cheuberg

Re: [sage-devel] Re: trac milestone

Am 2014-11-14 um 18:05 schrieb kcrisman: Per the recent discussion I will not batch modify the milestone on the currently-open tickets. Thank you. Did we end up discovering what the secret sauce was for doing it on the database directly? If the database schema at

merged in field of trac (was: Re: [sage-devel] Re: The Misfortunes of a Trio of Mathematicians Using Computer Algebra Systems)

Am 2014-11-13 um 17:46 schrieb kcrisman: Unfortunately, we no longer use the Merged in part of Trac, which was a VERY efficient way to find this out. Searching through git history and then trying to forward to the next release is something for git wizards, no doubt some command using tag...

[sage-devel] checkout for closed tickets which are not yet in develop

The release manager recently closed ticket #16747, but it is not yet in develop. In that time window, git trac checkout (or the equivalent git fetch trac commit_id) fails. $ git trac checkout 16747 Checking out Trac #16747 remote branch ec0aae9358f5204a3db6406b2c2f2818a78f5892 - local branch

[sage-devel] Re: checkout for closed tickets which are not yet in develop

, pressed the wrong buttons yesterday. Thanks for pointing it out. regards, CH. On Sat, Nov 15, 2014 at 6:16 PM, Clemens Heuberger clemens.heuber...@aau.at wrote: Am 2014-11-15 um 19:14 schrieb Volker Braun: Probably works: git remote update trac git trac checkout 16747 unfortunately, does

[sage-devel] Re: checkout for closed tickets which are not yet in develop

Am 2014-11-16 um 12:27 schrieb Volker Braun: On Sunday, November 16, 2014 6:34:56 AM UTC, Clemens Heuberger wrote: Works for me, possibly because I have a newer git. Can it be that it works for you because the commit ec0aae9358f5204a3db6406b2c2f2818a78f5892 (this is the actual

[sage-devel] How to include a module depending on an optional package into the reference manual?

In #17194, (rather minimal) bindings for the optional package Arb are provided. The module sage.rings.real_arb is only compiled if arb is actually installed, because otherwise, compilation would fail. Therefore, I cannot include sage/rings/real_arb into

Re: [sage-devel] Re: possible issue with DiGraph in interval fields

Am 2014-12-01 um 19:37 schrieb Nils Bruin: Interval fields apparently hide this (intervals are equal if they have non-empty intersection?), but of course hash cannot respect this, because this ComplexIntervalFieldElement.__richcmp__ says: As with the real interval fields this never

[sage-devel] Confusing documentation in element.pyx

In http://www.sagemath.org/doc/reference/structure/sage/structure/element.html#how-to-define-a-new-element-class , I find the descriptions of _add_ very confusing, because it seems to imply that there are two versions of _add_, one of them as a def and the other as a cpdef. As it stands, it

[sage-devel] Several arguments for RealIntervalFieldElement.min and .max

In #17198, I proposed a patch to have RealIntervalFieldElement.min (and .max) accept more than one other argument in order to compute the minimum (or maximum) of more than two RealIntervalFieldElements. It would also help me for another ticket (#17222) if someone could review this one. Thank

Re: [sage-devel] Confusing documentation in element.pyx

Am 2014-12-15 um 12:00 schrieb David Roe: The difference is in how cpdef functions interact with Cython vs Python classes. If you want to override a cpdef method in a *Python* subclass then you must use def (of course). But in a *Cython* subclass, you must use cpdef. If you accidentally

Re: [sage-devel] Confusing documentation in element.pyx

Am 2014-12-17 um 10:47 schrieb Samuel Lelievre: Hello! Your rewording mentions four relevant functions but I can only see three listed. thank you, I forgot to change that after unifying two descriptions. Fixed (http://trac.sagemath.org/ticket/17480 ). Also, there is a typo: DD NOT for DO

[sage-devel] Citing the same paper in docstrings of two different methods

one module to the other. - rename one of the occurrences to [HKP2015a]. Are there other options? What are your recommendations? What about the same question for different methods in one module? Thank you, CH -- Univ.-Prof. Dr. Clemens HeubergerAlpen-Adria-Universität Klagenfurt

Re: [sage-devel] cross-post from flint-devel: python bindings for Flint and Arb (work in progress)

this trivial to install into an existing Sage install? E.g. a sage package? Since you know where FLINT is there, what the version is, have the SAGE_LOCAL variable, etc... I could create an spkg. Later this month, hopefully. Note that Clemens Heuberger has started working on proper Sage

[sage-devel] sage -n ipython broken

From 6.5.rc0 on, sage -n ipython does no longer work, it starts the sagenb notebook with directory ipython.sagenb. Until 6.5.beta6, this opened the ipython notebook. sage -n -h says: --notebook [NOTEBOOK], -n [NOTEBOOK], -notebook [NOTEBOOK] The notebook to run

[sage-devel] Re: sage -n ipython broken

On 2015-02-11 15:06, Volker Braun wrote: Can you open a ticket? http://trac.sagemath.org/ticket/17769 regards, CH -- 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] matrix_template.pyx

http://www.sagemath.org/doc/reference/matrices/sage/matrix/docs.html#implementation-and-design mentions See the files matrix_template.pxd and matrix_template.pyx. However, I could not find these files. If they do not exist: is there a recommended example to follow when I implement bindings for

Re: [sage-devel] matrix_template.pyx

On 2015-02-23 10:59, Vincent Delecroix wrote: I would look at matrix_integer_dense.pyx which wraps fmpz_mat from flint (which looks even better after #17822 (needs review)). thanks for the hint. Are there also arb's polynomial? Yes, arb provides polynomials

Re: [sage-devel] Re: matrix_template.pyx

On 2015-02-23 11:25, Dima Pasechnik wrote: On 2015-02-23, Clemens Heuberger clemens.heuber...@aau.at wrote: http://www.sagemath.org/doc/reference/matrices/sage/matrix/docs.html#implementation-and-design mentions See the files matrix_template.pxd and matrix_template.pyx. However, I could

Re: [sage-devel] what should be in RIF?

Am 2015-03-19 um 17:32 schrieb William Stein: On Thu, Mar 19, 2015 at 2:48 AM, Ralf Stephan gtrw...@gmail.com wrote: sage: RIF(1/5) == RIF(1/5) False What's going on there? I don't know. But let's sort out why RIF(1/5) isn't equal to itself. Even more surprising Two

Re: [sage-devel] Can't build Sage with 2GB RAM anymore

. For more options, visit https://groups.google.com/d/optout. -- Univ.-Prof. Dr. Clemens HeubergerAlpen-Adria-Universität Klagenfurt Institut für Mathematik, Universitätsstraße 65-67, 9020 Klagenfurt, Austria Tel: +43 463 2700 3121Fax: +43 463 2700 99 3121

[sage-devel] Re: pushing to tickets after setting it to positive_review is incompatible with the current workflow

Am 2015-04-19 um 01:10 schrieb Volker Braun: Freezing tickets once release manager starts merging them - change status to closed - some new status) I'm happy to switch to closed when I merge it, and not only when it tests ok. +1 The downside is that you'll

Re: [sage-devel] Re: sage 6.6 pyopenssl

On 2015-05-04 10:55, Volker Braun wrote: We intentionally deleted the pyopenssl spkg. If it can be found on a mirror then that is only because it hasn't been updated. This is http://trac.sagemath.org/ticket/18261 I am not too happy that the instructions in the documentation of the

[sage-devel] sage 6.6 pyopenssl

I tried to install pyopenssl in order to run sagenb in sage 6.6 with secure=True. It fails with Error 404, see below. Regards, CH I get: $ ./sage -i pyopenssl Attempting to download package pyopenssl Checking online list of optional packages. [.] Found pyopenssl-0.13.p0 Trying to download

Re: [sage-devel] Re: pushing to tickets after setting it to positive_review is incompatible with the current workflow

Am 2015-05-07 um 10:27 schrieb Jeroen Demeyer: On 2015-05-07 06:15, Clemens Heuberger wrote: Am 2015-05-07 um 03:42 schrieb leif: I might be wrong, but isn't it trivial to check whether the branch of a ticket changed (after you merged it into some preliminary release)? It is easy to check

Re: [sage-devel] Re: pushing to tickets after setting it to positive_review is incompatible with the current workflow

Am 2015-05-07 um 10:39 schrieb Jeroen Demeyer: On 2015-05-06 21:24, Volker Braun wrote: There is no reason that closed should be final, until the new branch is published we *can* always back. That doesn't mean that you *should* dump a pile of extra bookkeeping on me. Let me make it clear

Re: [sage-devel] cross-post from flint-devel: python bindings for Flint and Arb (work in progress)

the class with methods. Thank you, CH Am 2015-02-08 um 10:21 schrieb Clemens Heuberger: On 2015-01-08 18:49, Fredrik Johansson wrote: On Thu, Jan 8, 2015 at 5:19 PM, William Stein wst...@gmail.com wrote: On Thu, Jan 8, 2015 at 5:56 AM, John Cremona john.crem...@gmail.com wrote: http://fredrikj.net

Re: [sage-devel] Re: pushing to tickets after setting it to positive_review is incompatible with the current workflow

Am 2015-05-06 um 20:07 schrieb Jeroen Demeyer: On 2015-05-06 20:00, Clemens Heuberger wrote: I'm happy to switch to closed when I merge it, and not only when it tests ok. The downside is that you'll get more emails as I'll inevitably have to reopen tickets, but merging/unmerging

Re: [sage-devel] Re: sage 6.6 pyopenssl

Am 2015-05-04 um 12:46 schrieb Volker Braun: It didn't work, there is no deprecation period for removing bugs. I see. Sorry, that was not clear to me, neither here nor on the ticket. Regards, CH On Monday, May 4, 2015 at 11:14:43 AM UTC+2, Clemens Heuberger wrote: On 2015-05-04 10

[sage-devel] Re: pushing to tickets after setting it to positive_review is incompatible with the current workflow

Am 2015-04-19 um 01:10 schrieb Volker Braun: On Saturday, April 18, 2015 at 4:47:05 AM UTC-4, Clemens Heuberger wrote: Freezing tickets once release manager starts merging them - change status to closed - some new status) I'm happy to switch to closed when

Re: [sage-devel] Re: pushing to tickets after setting it to positive_review is incompatible with the current workflow

Am 2015-05-07 um 03:42 schrieb leif: I might be wrong, but isn't it trivial to check whether the branch of a ticket changed (after you merged it into some preliminary release)? It is easy to check. But what if it did change? This might lead to an infinite cycle, as outlined before. Regards, CH

Re: [sage-devel] Re: Broken links to doc already appearing

@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout. -- Univ.-Prof. Dr. Clemens HeubergerAlpen-Adria-Universität Klagenfurt Institut für Mathematik, Universitätsstraße 65-67, 9020 Klagenfurt, Austria

[sage-devel] Re: [sage-release] Sage 6.7 released: Error installing package gcc-4.9.2.p1

On two different machines (Ubuntu 14.04 and Ubuntu 12.04), I get the error Error installing package gcc-4.9.2.p1: configure: error: in `/local/sage/sage-6.7/local/var/tmp/sage/build/gcc-4.9.2.p1 /gcc-build': configure: error: C compiler cannot create executables See `config.log' for more

Re: [sage-devel] Re: [sage-release] Sage 6.7 released: Error installing package gcc-4.9.2.p1

on both machines, my problem went away after make distclean . Before, it was a git checkout, no upgrade. Strange. Regards, CH Am 2015-05-18 um 08:31 schrieb Clemens Heuberger: On two different machines (Ubuntu 14.04 and Ubuntu 12.04), I get the error Error installing package gcc-4.9.2.p1

Re: [sage-devel] Re: Race condition when closing tickets

out of interest, I downloaded http://trac.sagemath.org/query?status=closedcol=idcol=summarycol=statuscol=milestonecol=resolutioncol=changetimecol=commitorder=priority as a .csv file and wrote an ugly script to see whether the commitid (if present) is merged in 6.7.beta0. I then manually removed

Re: [sage-devel] Re: Race condition when closing tickets

Out of my previous list, there were some false positives (I somehow mishandled invalid tickets). Five incompletely merged tickets remained. Am 2015-04-16 um 07:20 schrieb Clemens Heuberger: ticket commit changed 15017 872e2bc0225b6929ed8cc052a63850c892abe723

[sage-devel] pushing to tickets after setting it to positive_review is incompatible with the current workflow

. Regards, Clemens Heuberger -- You received this message because you are subscribed to the Google Groups sage-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel

Re: [sage-devel] Re: Race condition when closing tickets

Am 2015-04-16 um 19:28 schrieb kcrisman: That said, now that I see part of the problem is not just people changing tickets, but changing *branches* and *keeping* positive review (or something analogous to this), I agree that is a different situation. So, here's my possibly buggy suggestion:

[sage-devel] Re: pushing to tickets after setting it to positive_review is incompatible with the current workflow

Am 2015-04-17 um 12:03 schrieb Nathann Cohen: - A one-week delay (*) between latest commit and merge. We make sure that every last-minute change has been made. It also gives more time for everybody to look at the branch. Reduces the risk of loosing commits, but does not exclude it. As an

[sage-devel] Race condition when closing tickets

Ticket #17221 http://trac.sagemath.org/ticket/17221#comment:20 #17221 had been set to positive_review before, then reopened, another change (2e62790e) was pushed at 2015-04-13T04:22:22-07 and then set to positive_review again. It was closed at 2015-04-14T12:44:07-07 with the

[sage-devel] Re: pushing to tickets after setting it to positive_review is incompatible with the current workflow

Am 2015-04-17 um 13:43 schrieb Volker Braun: I already proposed a cool-off period, possible but somewhat annoying. What about blockers? Would they also have to wait two weeks? Even after .rc3 is out with one trivial bug? Ideally, continuous integration would start merging your ticket the

[sage-devel] needs_review: #17220: Matrix_complex_ball_dense: Level 1 implementation (using acb_mat from Arb)

Dear all, I'd appreciate very much if somebody how knows how to implement matrices could review #17220: This ticket wraps arb's acb_mat (matrices over the complex balls), currently only with level 1 functionality in order to keep the patch within reasonable size. Thanks in advance, Clemens --

[sage-devel] Iterator over product of infinite iterators

countable sets is countable. Does such an iterator exist in sage? I found the sage.misc.mrange module, but I do not have the impression that it deals with infinite iterators. Regards, Clemens Heuberger -- You received this message because you are subscribed to the Google Groups "sage-

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

Am 2015-10-01 um 10:39 schrieb Jeroen Demeyer: > For a possible fix, see > http://trac.sagemath.org/ticket/19324 > (still needs testing) > > > Related: > http://trac.sagemath.org/ticket/19313 > probably related problems have been reported as

[sage-devel] How to force recompilation of a package after adding a patch

In #19280, I added a patch file to package mpir, the package itself and its version did not change. I can force manual recompilation of the package using sage -p (or sage -f). My question: how can I force recompilation of that package automatically? Say, if #19280 is merged in a beta release,

Re: [sage-devel] How to force recompilation of a package after adding a patch

Am 2015-09-25 um 09:11 schrieb Francois Bissey: > The trivial answer is the only way. But you don’t have to rename the tarball. Thank you. Out of curiosity: is there some magic involved which takes the tarball for 2.7.0 if the version ends on .p* and the checksum still matches or how does that

Re: [sage-devel] Finite State Machine Improvements

Hi, Am 2016-01-03 um 07:00 schrieb Marco Cognetta: > Hi, > > I would like to implement some of the closure operations that are missing from > the finite state machine code. Since there are several that are not > implemented > (intersection, difference, reversal, homomorphism, and inverse

[sage-devel] Trac - internal error

Trac detected an internal error: OSError: [Errno 2] No such file or directory: '/tmp/tmp7BmVNV' The action that triggered the error was: GET: /ticket/19306 -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop

[sage-devel] Trac Timeout

I'd like to set #19423 to positive_review, but cannot do so due to a trac timeout. I left the comment field empty. I can open trac ticket pages without problems, so it is a problem just with post. Regards, Clemens -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Re: error rebuilding sage

On 2016-02-04 23:25, Dima Pasechnik wrote: > > > On Thursday, 4 February 2016 21:00:03 UTC, jhonrubia6 wrote: > > How do I know the version of a given ticket which needs review? > > > typically for reviewing you don't even want to know, just merge over the > current > develop branch. >

[sage-devel] Conversion Jupyter Notebook -> Doctests

Is there a way to convert a jupyter notebook .ipynb to a "doctestable file"? Such a thing existed for the sage notebook. I would like to have that for two reasons: - once I am satisfied with computations in a notebook for a paper, I'd like to convert it and run doctests on it (e.g., with later

Re: [sage-devel] Reproducability of results

On 2016-02-24 04:48, Clemens Heuberger wrote: > On 2016-02-23 17:29, Clemens Heuberger wrote: >> I try to pinpoint the other examples and will then report those. > > Here is the next issue which I encountered: > > $ sage-6.9/sage -c "print bool((x^2 - 1 - (x+1)*(x-1

Re: [sage-devel] Reproducability of results

On 2016-02-23 16:57, Jeroen Demeyer wrote: > On 2016-02-23 15:50, Clemens Heuberger wrote: >> Bottom line: I cannot reproduce 11 month old results anymore. > > Personally, I think this is a flaw in the review process for Sage tickets. > Reviewers should check whether existin

Re: [sage-devel] Reproducability of results

On 2016-02-24 18:16, Jeroen Demeyer wrote: >> * What files are welcome there? > Anything which satisfies the rules on doctests (in particular, tests should > not > take too much time). What is the definition of "too much time"? Instead of the usual time per test (which is rather pointless

Re: [sage-devel] Reproducability of results

On 2016-02-23 17:29, Clemens Heuberger wrote: > I try to pinpoint the other examples and will then report those. Here is the next issue which I encountered: $ sage-6.9/sage -c "print bool((x^2 - 1 - (x+1)*(x-1)) != 0)" False $ sage-6.10/sage -c "print bool((x^2 - 1 - (x+1)*(x-

Re: [sage-devel] GSOC 2016-Regression test framework

On 2016-02-26 04:50, Jayamine A. wrote: > But when we are dealing with clients(users) we need both.(My opinion) That was basically my opinion in the thread https://groups.google.com/d/topic/sage-devel/ojHqBy7oUVU/discussion Clemens -- You received this message because you are

[sage-devel] jupyter may die with old ipynb file (was: Reproducability of results)

On 2016-02-23 17:29, Clemens Heuberger wrote: > I try to pinpoint the other examples and will then report those. I finally had a fourth issue in this saga. If you used jupyter in Sage 6.9 on your machine and the directory containing Sage 6.9 no longer exists, opening a jupyter file saved by S

Re: [sage-devel] Reproducability of results

On 2016-02-23 16:57, Jeroen Demeyer wrote: > On 2016-02-23 15:50, Clemens Heuberger wrote: >> It is also impossible to compile Sage 6.5 nowadays > > I assume this was a build from git? That's indeed not supported. A real > build-from-source-tarball should still work. yes, I t

[sage-devel] Reproducability of results

I am currently revising a paper that I submitted in March 2015. Parts of the results heavily rely on computations in Sage; at that time, Sage 6.5. It turns out that the old code no longer works with Sage 7.0. It is also impossible to compile Sage 6.5 nowadays because the infrastructure changed

Re: [sage-devel] Request to extend the binomial function by the reflection formula

Am 2016-04-04 um 18:02 schrieb Peter Luschny: > > Sage seems to use the definition from Concrete Mathematics by Graham, >> Knuth and Patashnik: >> That gives e.g. >> sage: binomial(-4, 5) >> -56 > > Right. GKP call it "upper negation". If you look at my demo-function > you will see that

Re: [sage-devel] Deprecate the use of properties in all public API (was: Heavy-computation @property in Matrix class)

[X] Phase out properties which perform any non-trivial computation, and officially condone the use of properties as "getters" of trivial private information. Best, Clemens -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

Re: [sage-devel] Re: Organisation of online : survey of developers

Am 2017-02-05 um 03:22 schrieb kcrisman: > > "Tutorial", "Thematic Tutorial", "PREP Tutorial", "A Tour of Sage". and > "Constructions" are mostly the same Tutorial. > > > Just for clarification, these are massively and completely different > documents. > There is also a lot of

[sage-devel] Crash in smith_normal_form

Roswitha Rissner found a 25x26 matrix over GF(3)[x] such that calling smith_form() leads to a crash: *** Error in `python': free(): invalid next size (normal): 0x03ad4fe0 *** Input file as well as the full output are below. The mathematical problem itself does seem to be solvable: pari

Re: [sage-devel] Python 3: in #22398

Am 2017-02-22 um 10:43 schrieb Daniel Krenn: > On > https://trac.sagemath.org/ticket/22398 > the python3-plugin of the patchbot fails in the doctest *output* line > (, ) > because it includes "". We want to check types there; this > is the corresponding input line: > sage: type(k), type(v) >

[sage-devel] Re: Timeouts on patchbots

Am 2017-02-13 um 19:44 schrieb Jakob Kroeker: > It is my subjective observation that timeouts on patchbots have become > more > frequent. For instance, for ticket > https://patchbot.sagemath.org/ticket/22340/ > > two

[sage-devel] Timeouts on patchbots

It is my subjective observation that timeouts on patchbots have become more frequent. For instance, for ticket https://patchbot.sagemath.org/ticket/22340/ two patchbots failed due to timeout, quasar times out with sage: ls = J0(46)._calculate_endomorphism_generators() ; ls ## line 213 ##

Re: [sage-devel] py3 build and a c++ error

Am 2017-02-09 um 19:32 schrieb Daniel Krenn: > On 2017-02-09 18:10, Frédéric Chapoton wrote: >> There are currently two conflicting semantics for cmp and <, namely cmp >> is lexicographic order, whereas < is some custom relation inspired by >> the semantics of fuzzy numbers. I could even imagine

[sage-devel] Factorisation bug

Is this a known bug? sage: R. = ZZ[] sage: ((9*k*K^7- 3*k*K^5 + 9*K)/(2*(2*K+1))).factor() Traceback (most recent call last): ... TypeError: Cannot multiply 3 * K * (3*K^6*k - K^4*k + 3) and 2^-1 * (2*K + 1)^-1 because they cannot be coerced into a common universe Regards, Clemens

Re: [sage-devel] Factorisation bug

at 15:07, Clemens Heuberger > I would say that was a bug. Change ZZ to QQ and it is fine. I still consider the current behaviour to be a bug, especially in view of the better behaviour of the univariate ring. In particular, throwing a TypeError seems to be quite inappropriate here. I us

Re: [sage-devel] Re: sage -br rebuilds things that were not changed

Am 2016-09-11 um 04:01 schrieb Daniel Krenn: > On 2016-09-10 18:36, Johan S. H. Rosenkilde wrote: >> Without this or a similar schema, working on multiple tickets becomes >> absolutely unbearable for me due to compilation time. How do you guys >> cope with that? > > Having a version of each

Re: [sage-devel] hash of QQbar inefficient

-0.01))) Computation of the hash takes very long (I stopped after a few minutes); changing QQbar_hash_offset leads to an immediate answer. Best regards, Clemens > > Ciao, > Thierry > > > > > On Tue, Oct 04, 2016 at 07:57:37PM +0800, Clemens Heuberger wrote: >

[sage-devel] hash of QQbar inefficient

Hashing of QQbar elements seems to be quite inefficient: sage: R. = AA[] sage: rho = QQbar.polynomial_root( : x^5 - 1/3*x^4 + 1/30*x^3 - 1/600*x^2 + 1/24000*x - 1/240, : CIF(RIF(0.02, 0.03), RIF(-0.009, -0.007))) sage: %time hash(rho) CPU times: user 14 s, sys: 36 ms, total:

[sage-devel] gamma(QQbar(...))

I was surprised by the following behaviour: sage: gamma(QQbar(sqrt(2))) 0.886581428719259 sage: gamma(QQbar(sqrt(2))).parent() Complex Field with 53 bits of precision (I would have preferred to have some symbolic answer or at least an answer in CIF, but not in CC) Furthermore: sage:

[sage-devel] doctesting and sys.path

I have two .py files (not in the library) in the same directory where one imports the other. I'd like to run doctests, but the local directory does not seem to be in the search path. Is there any way of doing this apart from fiddling around with sys.path in the .py files themselves? Minimal

[sage-devel] AlgebraicReal.minpoly slow

I am running x = polygen(QQ) equation = -96000*x^7 + 41600*x^6 - 6640*x^5 + 560*x^4 - 28*x^3 + 8400*x^2 - 140*x + 1 roots = equation.roots(QQbar) a_root = roots[-1][0] abs_root = abs(a_root) %time abs_root.minpoly() and am surprised that it takes approx. three minutes.

Re: [sage-devel] Re: AlgebraicReal.minpoly slow

Am 2016-09-20 um 20:22 schrieb Marc Mezzarobba: > Clemens Heuberger wrote: >> x = polygen(QQ) >> equation = -96000*x^7 + 41600*x^6 - 6640*x^5 + 560*x^4 >> - 28*x^3 + 8400*x^2 - 140*x + 1 roots = equation.roots(QQbar) >> a_root = roots[-1][

Re: [sage-devel] Re: Checking out old branches

On 2016-11-18 10:05, David Roe wrote: > > > On Fri, Nov 18, 2016 at 3:49 AM, Volker Braun > wrote: > > The .git dir doesn't have to be in the working tree: > > git --git-dir= --work-tree= > > But I think its very confusing to

[sage-devel] patchbot: ticket list latency?

I am playing around with a patchbot and I am wondering whether there is some kind of caching or other latency involved with the tickets which are available for testing. For instance, ticket #21992: the branch was last changed 25 hours ago; 6 hours ago it was set to positive review. However,

[sage-devel] Re: patchbot: ticket list latency?

Hello, On 2017-01-05 17:29, Frédéric Chapoton wrote: > Tickets with untrusted authors are never looked at, unless you ask > specifically so : > { > "Clemens Heuberger": "trusted", > "Roswitha Rissner": "not trusted" > } that's

Re: [sage-devel] Re: patchbot: ticket list latency?

On 2017-01-07 23:22, Vincent Delecroix wrote: > Le 05/01/2017 à 18:05, Clemens Heuberger a écrit : >> >> Hello, >> >> On 2017-01-05 17:29, Frédéric Chapoton wrote: >>> Tickets with untrusted authors are never looked at, unless you ask >>> speci

  1   2   >