Re: [sage-devel] Map, Morphism and PoorManMap

On Mon, Jun 15, 2015 at 12:07 AM, 'Martin R' via sage-devel < sage-devel@googlegroups.com> wrote: > Hi there! > > I would like to understand the (intended) purpose of the three classes > Map, Morphism and PoorManMap. > > What I know so far: > > * Morphism inherits from Map, and provides a few more

Re: [sage-devel] Re: matrix constructor signature clash

Another option might be to force certain construction paths to use keyword arguments. For example, matrix(4,4,scalar = x+y) matrix(4,4,iterator = x+y) David On Fri, Jun 19, 2015 at 11:03 AM, Nils Bruin wrote: > On Friday, June 19, 2015 at 9:10:41 AM UTC-7, Darij Grinberg wrote: >> >> > Unfortun

Re: [sage-devel] Re: a sage bug

> By the way, does anybody know what the deal is with: "Please forgive > me to send it to you for I am in China and have a problem to access > Google groups." > > Do most people in China really not have access to Google groups? If > so, that's a very good reason for us to consider at least some so

Re: [sage-devel] Re: is_zero proof survey

It depends on exactly what you mean by undecidable, but this is the definition of an inexact ring in some sense. So, p-adics, power series rings, reals David On Fri, Jul 17, 2015 at 1:34 AM, Volker Braun wrote: > On Friday, July 17, 2015 at 10:25:29 AM UTC+2, Ralf Stephan wrote: >> >> 1. Can

Re: [sage-devel] ./configure && make for Sage

On Fri, Jul 24, 2015 at 10:02 AM, Jeroen Demeyer wrote: > Hello, > > usually, autotools-based packages are built using > > ./configure > make > > which for Sage this has historically been just "make". However, I think that > Sage should move to the "./configure && make" model, for various reasons:

Re: [sage-devel] Log behavior

It's because Integer(8) has a log method, while int(8) does not. Line 322-324 of sage/functions/log.py are try: return args[0].log(base) except (AttributeError, TypeError): David On Fri, Jul 24, 2015 at 2:39 PM, Jeremy Martin wrote: > The following looks weird: > > sage: log(int(8)

Re: [sage-devel] Re: Log behavior

> Moreover, do we really want > > sage: log(QQ(8), 2).parent() > Integer Ring I would say yes. For rational x which is not a power of 2, log(x, 2) will end up in the symbolic ring. But we should avoid this if possible, and the only logs which are rational will actually be integral, so we might a

Re: [sage-devel] PolynomialQuotientRing_generic not a QuotientRing_generic

We used to try to describe mathematical properties through Python inheritance, but have since shifted to using Sage's category framework. So I don't think that there's a particularly strong reason to choose either CommutativeRing or QuotientRing_generic to inherit from. Of course, as a Python cl

Re: [sage-devel] PolynomialQuotientRing_generic not a QuotientRing_generic

ynomial ring, a polynomial ring happens to be > univariate, a field happens to have characteristic 2). Object orientation > could be useful in preventing this from happening but maybe so can Sage's > category framework?) > > > On 11.08.2015 18:42, David Roe wrote: >> >>

Re: [sage-devel] matrix.subs()

On Sat, Aug 15, 2015 at 3:00 AM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Hello, > > As mentioned by Søren on ask [1] the subs method of matrices behave > differently than the subs method on coefficients > > sage: R. = PolynomialRing(ZZ) > sage: m = matrix(R, [[x]]) > > sage: x.

Re: [sage-devel] Integer from mpz_t

Since you have an mpz_t, presumably you're writing in Cython. Then you can do something like the following. cdef mpz_t input cdef Integer output = PY_NEW(Integer) output.set_from_mpz(input) Or something like mpz_set(output.value, input). David On Wed, Aug 19, 2015 at 2:19 AM, Ralf Stephan wro

Re: [sage-devel] Why am I getting tons of old sage-trac emails?

Frédéric Chapoton was removing tab characters from the description field on lots of old tickets. He has since stopped, upon request. There's a recent thread about an alternate solution to the problem he was trying to solve. David On Mon, Sep 7, 2015 at 12:56 AM, Dr. David Kirkby (Kirkby Microwave

Re: [sage-devel] Default precision for floats

One approach would be to change "RealNumber('%s')" % num on line 739 of sage.repl.preparse to "RealNumber('%s',min_prec=1000)" % num. David On Sat, Sep 12, 2015 at 12:24 PM, Thierry Dumont wrote: > I have a program with a lot of floating point constants/variables (this is a > translation of a C++

Re: [sage-devel] Re: *.math.washington.edu hardware resources

On Thu, Sep 17, 2015 at 6:05 PM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > > > On 17/09/15 17:10, William Stein wrote: >> >> On Thu, Sep 17, 2015 at 1:04 PM, kcrisman wrote: > it would be useful to revive the discussion of a > true SageMath Foundation, separate from

Re: [sage-devel] Whats the plan for random doctests with floating point numbers?

We already have a relative tolerance check available: sage: print("0.")# rel tol 1e-4 1.0 sage: print("1.1") # abs tol 1e-5 1.0 David On Thu, Dec 30, 2021 at 2:42 PM tobia...@gmx.de wrote: > It would also be an idea to replace these absolute tolerance tests, i.e. > abs(x - y) < so

Re: [sage-devel] sage -t: sorting sources by runtime

This is for when you're running in parallel, so that you don't start a file that takes a long time at the end of the run. David On Tue, Feb 8, 2022 at 9:50 PM Michael Orlitzky wrote: > > Sorting sources by runtime so that slower doctests are run first > > Doctesting 4320 files... > > Why? Do

[sage-devel] First object printed in Sage session is slow

sage: %time s = display(1) 1 CPU times: user 677 ms, sys: 31.1 ms, total: 708 ms Wall time: 708 ms In other words, the first object you display in a Sage session takes almost a second. This is new since 9.4 (I don't have 9.5 betas to check against). The problem is not specific to 1: anything you

Re: [sage-devel] Can we restore `mean`?

The documentation of Python's statistics module notes that "Unless explicitly noted, these functions support int, float, Decimal and Fraction. Behaviour with other types (whether in the numeric tower or not) is currently unsupported. Collections with a mix of types are also undefined and implementa

Re: [sage-devel] any([magma(True),magma(True)]) produces stack overflow

This should have been fixed in https://trac.sagemath.org/ticket/32602. David On Fri, Feb 18, 2022 at 2:58 PM 'Justin C. Walker' via sage-devel < sage-devel@googlegroups.com> wrote: > > > > On Feb 18, 2022, at 08:09 , Simon Brandhorst wrote: > > > > ``` > > sage: any([magma(True),magma(True)]) >

Re: [sage-devel] Can we restore `mean`?

...@gmail.com> wrote: > Le 13/02/2022 à 22:21, Matthias Koeppe a écrit : > > On Sunday, February 13, 2022 at 12:58:41 PM UTC-8 David Roe wrote: > > > >> The documentation of Python's statistics module notes that "Unless > >> explicitly noted, these functi

Re: [sage-devel] divmod() vs .quo_rem()

I see no reason why Sage couldn't support divmod() in addition to quo_rem(). David On Tue, Apr 12, 2022 at 9:46 AM Lorenz Panny wrote: > > Python defines divmod() and the associated .__divmod__() magic method > for what Sage calls .quo_rem(). > > Is there any reason why Sage shouldn't or cannot

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

I haven't been following the copy and paste thread, but I'm in favor of keeping sage -i xyz functional, even at the cost of some hacks in our codebase. There are a lot of existing Sage users who are familiar with that command as a mechanism to install optional packages, even if it's not a priori d

Re: [sage-devel] Re: [sage-release] Re: Sage 9.5 released

On Mon, Apr 25, 2022 at 2:54 PM Matthias Koeppe wrote: > All - https://www.sagemath.org/ now has a revised Download menu - please > take a look. > (thanks to Harald for merging my PR > https://github.com/sagemath/website/pull/238 > Very nice! Is there a way to set up our DNS so that the url is

Re: [sage-devel] Re: Closing the old Sage wiki

On Thu, Apr 28, 2022 at 2:19 AM Matthias Koeppe wrote: > An update: > > I have re-organized the front page of https://trac.sagemath.org/ > and have migrated a number of development-related pages from > the old wiki - https://wiki.sagemath.org/RecentChanges > Overall I like the changes, but here

Re: [sage-devel] The SageMath developer map needs your (updated) information

For former contributors who are no longer active, do we have a policy about saying their current institution/company versus where they were when they were contributing to Sage? David On Mon, May 9, 2022 at 3:51 AM Dima Pasechnik wrote: > On Sun, May 8, 2022 at 9:51 PM Matthias Koeppe > wrote: >

Re: [sage-devel] Question about factories, representations and multiple classes

I think the following should work: class MyObject: def __classcall__(cls, arg): if isinstance(arg, special): return typecall(MyObject_specific_case, arg) else: return typecall(MyObject, arg) plus the same __init__ you had before. I haven't checked

Re: [sage-devel] Re: Polling for pygments style for our future doc

default > sphinx > tango. I agree that the italics are the main issue with tango; I like the color scheme more than the other two. David On Thu, Aug 4, 2022 at 11:00 AM Eric Gourgoulhon wrote: > Le jeudi 4 août 2022 à 18:33:27 UTC+2, Eric Gourgoulhon a écrit : > >> Thanks for preparing this pol

Re: [sage-devel] Re: Proposal: make Furo a standard package

On Thu, Aug 4, 2022 at 10:29 AM Eric Gourgoulhon wrote: > Le jeudi 4 août 2022 à 03:29:07 UTC+2, Kwankyu Lee a écrit : > >> So we propose here to upgrade the Furo package to a standard package. >> Please vote. > > > +1 > Thanks for working on this. > +1 for Furo as standard from me as well. Davi

Re: [sage-devel] Re: Polling for sphinx background style

Same: grayish > detoned > original. David On Thu, Aug 4, 2022 at 9:45 PM Matthias Koeppe wrote: > grayish >> detoned > original > > On Thursday, August 4, 2022 at 8:42:35 PM UTC-7 Matthias Koeppe wrote: > >> I didn't see a difference until I realized I need to switch to light mode >> >> >> >> On

Re: [sage-devel] Solving quintics

Hi Achim, Many of the polynomials you mention can be factored by Sage if you use number fields for your coefficients rather than the symbolic ring. For example: sage: R. = ZZ[] sage: K. = NumberField(x^2 + x + 1) sage: f = x^5 + 9/2 * x^4 - 5/2 * x^3 - 2*w * x^2 - 9*w * x + 5*w sage: f.factor() (

Re: [sage-devel] Bug in decomposition_type

Thanks for the report. There's a fix at #34514 , needs review. David On Fri, Sep 9, 2022 at 5:17 AM Björn Selander wrote: > Hi, > > running the Sage script > > K. = NumberField(x^4 + 18*x^2 - 1) > R. = K[] > L. = K.extension(y^2 + 9*a^3 - 2*a^2 + 162*a -

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

While I strongly support the shift to github, I also agree with Travis that we should vote on a change this major, and give the community enough time to weigh in. I would also encourage people on both sides of the debate to give everyone the benefit of the doubt. To those who have been putting in

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

On Tue, Sep 13, 2022 at 3:57 AM 'Travis Scrimshaw' via sage-devel < sage-devel@googlegroups.com> wrote: > > On Tuesday, September 13, 2022 at 4:14:26 PM UTC+9 Matthias Koeppe wrote: > >> On Tuesday, September 13, 2022 at 12:10:28 AM UTC-7 Travis Scrimshaw >> wrote: >> >>> How is the workflow that

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

My understanding from the allowing-changes-to-a-pull-request-branch-created-from-a-fork documentation is that only users who have push permiss

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

On Tue, Sep 13, 2022 at 6:36 PM Dima Pasechnik wrote: > > > > > > > On Tue, 13 Sep 2022, 23:03 Matthias Koeppe, > wrote: > >> On Tuesday, September 13, 2022 at 3:01:14 PM UTC-7 Thierry >> (sage-googlesucks@xxx) wrote: >> >>> Also, several people have already explicitely requested for a break (if

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

I've started working on a list of pros and cons to be included in the email proposing a vote. Even though I favor the switch, I've tried to accurately and neutrally describe the arguments in each direction. I welcome help and additi

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

Given that we've had far more interest in Github than Gitlab, and that it's a lot easier to transfer from Github to Gitlab later, I agree with Dima that the vote should be on just the question of whether to move to Github. Moreover, John Palmieri made a convincing argument (to me at least) that we

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

is a broader question related to Sage's governance, but one objective criterion I can think of would be "ever made a code contribution to Sage." David > -- William > > On Mon, Sep 19, 2022 at 2:10 PM David Roe wrote: > > > > Given that we've had far more in

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

When I did this a few weeks ago there were only a couple hundred. I think it's only showing people who have a github account linked to the email they used on the commit (which may be lower than normal, since grad students and postdocs may have used academic email accounts that are no longer active

[sage-devel] VOTE: move Sage development to Github

Dear Sage developers, Following extensive discussion, both recently (prompted by issues upgrading the trac server) and over the

[sage-devel] DISCUSS: move Sage development to Github

Dear Sage developers, As announced in a parallel thread, we are voting to move Sage development from Trac to Github. Several of us have created a wiki page attempting to summarize arguments in favor of each system, and this thread ca

Re: [sage-devel] VOTE: move Sage development to Github

+1 for Github On Wed, Sep 21, 2022 at 1:36 PM William Stein wrote: > +1 for Github > > On Wed, Sep 21, 2022 at 10:23 AM David Roe wrote: > > > > Dear Sage developers, > > Following extensive discussion, both recently (prompted by issues > upgrading the trac server

Re: [sage-devel] DISCUSS: move Sage development to Github

ewhere (not every contributor to Sage or its > dependencies/packages is there) ? > > On Wed, Sep 21, 2022 at 6:23 PM David Roe wrote: > > > > Dear Sage developers, > > As announced in a parallel thread, we are voting to move Sage > development from Trac to Github

Re: [sage-devel] DISCUSS: move Sage development to Github

This is Github's documentation for doing it, but it's pretty annoying: https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors Maybe we could create some automation to add these kinds of comments to the merge

Re: [sage-devel] Re: is it intentional that prod does not stop when it hits 0?

On Fri, Sep 23, 2022 at 4:39 AM 'Martin R' via sage-devel < sage-devel@googlegroups.com> wrote: > @chris: that's a great point. Although I thought that the convention for > "_bool_" is to return False only if it provably False, and otherwise True? > That's not the convention for p-adics: sage:

Re: [sage-devel] Re: specification of __bool__

Nils put it well; please don't change __bool__ for p-adic and power series. It should be compatible with equality testing. David On Tue, Sep 27, 2022 at 11:44 AM Nils Bruin wrote: > It seems attractive that for numerical types, bool(a) gives that same > result as "not(a==0)", which would hopefu

Re: [sage-devel] Re: VOTE: move Sage development to Github

-migrating to self-hosted Gitlab. > > Le mercredi 21 septembre 2022 à 19:23:36 UTC+2, David Roe a écrit : > >> Dear Sage developers, >> Following extensive discussion, both recently >> <https://groups.google.com/g/sage-devel/c/ayOL8_bzOfk/m/Pg-rmYAUBwAJ> >> (

Re: [sage-devel] Re: VOTE: move Sage development to Github

Just a reminder that voting ends tomorrow (noon EDT, 16:00 UTC), so if you've been putting off voting you should do so now. David On Tue, Oct 4, 2022 at 7:39 AM Alex J Best wrote: > +1 for github > > On Wednesday, September 21, 2022 at 7:23:36 PM UTC+2 David Roe wrote: > >&g

Re: [sage-devel] Re: VOTE: move Sage development to Github

Thanks to everyone for voting! The final results are 46 in favor of moving to Github and 8 against. There is still a lot of work to be done to carry out the transition, and we'll be coordinating on this wiki page and this trac

Re: [sage-devel] Re: Democratic issue: rushing decisions

I will also note that the final vote in favor of moving to github was 46 to 8 in favor. Another few weeks of discussion, on top of the substantial amount of time spent over the last few months (in fact, over the last decade), is unlikely to have changed the outcome. David On Wed, Oct 5, 2022 at 1

Re: [sage-devel] missing coercion?

Yes, that's expected. sage: P = PolynomialRing(GF(2), "z", sparse=True); Q = PolynomialRing(ZZ, "z", sparse=True) sage: P.has_coerce_map_from(Q) True And of course you can convert even when Q is not sparse. David On Wed, Oct 12, 2022 at 4:58 PM 'Martin R' via sage-devel < sage-devel@googlegroups

Re: [sage-devel] missing coercion?

ialRing(GF(2), "z", sparse=True); Q = PolynomialRing(ZZ, > "z", sparse=False) > sage: P.has_coerce_map_from(Q) > False > > How does this fit with > > "And of course you can convert even when Q is not sparse."? > > Martin > > On Wednesday,

Re: [sage-devel] sage is slowding down PARI/GP by factor x2 (roughly)

It could be related to #31572 , which notes a dramatic speed regression based on pari being compiled with pthread. David On Wed, Dec 14, 2022 at 3:30 PM Dima Pasechnik wrote: > I vaguely recall something about the way gp is built, without linking > libpari

Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

I am still able to edit comments (see https://trac.sagemath.org/ticket/11777#comment:5), but there doesn't seem to be a way to edit the ticket's overall status. I think this is probably alright, if you're struggling to figure out how to disable editing comments. David On Mon, Jan 30, 2023 at 11:0

Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

Unfortunately, I was still able to edit the comment. David On Mon, Jan 30, 2023 at 12:49 PM Dima Pasechnik wrote: > On Mon, Jan 30, 2023 at 4:12 PM David Roe wrote: > > > > I am still able to edit comments (see > https://trac.sagemath.org/ticket/11777#comment:5), but there do

Re: URGENT: Re: [sage-devel] Jan 30 to Feb 4: Trac downtime, migration to GitHub

I haven't been logged out, and am still able to edit my comments. David On Mon, Jan 30, 2023 at 3:41 PM Dima Pasechnik wrote: > On Mon, Jan 30, 2023 at 8:38 PM Kwankyu Lee wrote: > > > > On Tuesday, January 31, 2023 at 5:15:24 AM UTC+9 dim...@gmail.com wrote: > > that's cause I have to run "tra

Re: [sage-devel] Creating a github team

On Tue, Feb 7, 2023 at 10:28 AM Eric Gourgoulhon wrote: > Hi, > > Thanks again for all the hard work for the github migration! > > I would like to create a team "Manifolds" of https://github.com/sagemath, > with sufficient permissions so that I can add users to it. How shall I > proceed? Are ther

Re: [sage-devel] Stepping away for a bit

Thank you so much for your work on this transition Matthias! David On Mon, Feb 6, 2023 at 9:34 PM Dima Pasechnik wrote: > > > On Mon, Feb 6, 2023 at 8:17 PM Matthias Koeppe > wrote: > > > > Dear Sage developers, > > As the migration of the Trac tickets to GitHub issues was completed > yesterday

Re: [sage-devel] Creating a github team

members? (Or is > that against the spirit of open source?) Then, a new contributor would > first ask to become a member, and then would be able to make a PR. > > John > > On Tue, 7 Feb 2023 at 16:29, Eric Gourgoulhon > wrote: > >> Thanks for your reply. >> &g

[sage-devel] Merging fix for github CI

Hi all, Currently, almost all of the PRs on github aren't passing CI, and thus have red Xs. The problem can be resolved by merging #34964 and #34987 . Several of us

Re: [sage-devel] Merging fix for github CI

ng time tags > > #34964 trims some whitespace and changes "" to r""" in a few necessary > places. > > > > On Tue, 7 Feb 2023 at 18:18, David Roe wrote: > >> > >> Hi all, > >> Currently, almost all of the PRs on github aren't

[sage-devel] Adding labels to github issues

Yesterday I manually added a bunch of people that I recognized to the sagemath organization triage team on github, which gives people the ability to edit labels. I don't intend to exclude any active Sage developers, so if you want to be able to chang

Re: [sage-devel] Merging fix for github CI

s >>>> protected, you can't push/merge there (I can, as Admin, though)) >>>> >>>> Perhaps that was due to the base branch being so old, that no branch >>>> info on that was computed by GitHub ahead of my fetch. >>>> >>>>

Re: [sage-devel] fetch from draft PR not working

You probably want ```git fetch upstream pull/35008/head:covering_array``` Your fork of Sage (origin) doesn't include all of the PRs from the upstream repository. David On Wed, Feb 8, 2023 at 8:40 PM brettpim wrote: > I have followed the Provisional workflow on GitHub >

Re: [sage-devel] fetch from draft PR not working

w on GitHub > <https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md#issue-with-pr> > instructions? > > thanks > brett > > On Wednesday, February 8, 2023 at 2:54:07 PM UTC-5 David Roe wrote: > >> You probably want >> ```git fe

Re: [sage-devel] Re: New wiki at sagemath/sage hosted by GitHub

Has any content from https://wiki.sagemath.org/ been moved to the github wiki, or is that planned? David On Thu, Feb 9, 2023 at 2:08 AM Kwankyu Lee wrote: > The url is > > https://github.com/sagemath/sage/wiki > > -- > You received this message because you are subscribed to the Google Groups > "

Re: [sage-devel] reviewer role on github

I think the interface only allows reviewers for PRs, and not for issues (though you could always make a comment on an issue declaring your intention to review any resulting PR). For PRs, you have a couple options: 1. At the top right of the PR, there's a "Reviewers" box, with a gear icon next to i

Re: [sage-devel] Re: reviewer role on github

Permission-wise, I think the only required permissions to review are Read permissions, so I don't think it should be technically restricted. David On Fri, Feb 10, 2023 at 11:33 AM 'Martin R' via sage-devel < sage-devel@googlegroups.com> wrote: > In which repository? > > Does this mean that resear

Re: [sage-devel] Re: reviewer role on github

On Fri, Feb 10, 2023 at 11:50 AM Kwankyu Lee wrote: > On Friday, February 10, 2023 at 7:33:51 PM UTC+9 Martin R wrote: > In which repository? > > Here: https://github.com/sagemath/sage/issues > > Does this mean that researchers cannot become reviewers immediately > anymore? > > You first become a

Re: [sage-devel] Confused about power series ring identity

On Fri, Feb 17, 2023 at 6:04 AM Nils Bruin wrote: > From "PowerSeriesRing" docstring: > >There is a unique power series ring over each base ring with given >variable name. Two power series over the same base ring with >different variable names are not equal or isomorphic. > > However

Re: [sage-devel] Procedure to be a member of sage github organization

As a first proposal: once you have a PR accepted then you're added to the sagemath organization. I'm not sure exactly what the cutoff should be for being added to triage (which gives the capability of changing labels, closing and assigning issues and PRs, requesting PR reviews, applying milestones

Re: [sage-devel] Re: Adding labels to github issues

not figure out how to do. > > regards > brett stevens > > On Wednesday, February 8, 2023 at 7:51:40 AM UTC-5 David Roe wrote: > >> Yesterday I manually added a bunch of people that I recognized to the >> sagemath organization triage team >> <https://github.co

Re: [sage-devel] Adding labels to pull requests?

Hi Enrique, I've added you to the Triage team, so now you can manage labels. David On Wed, Mar 29, 2023 at 1:33 PM enriqu...@gmail.com wrote: > Actually I have the same problem, I cannot see how to apply labels to PR I > created. Maybe I can't. Thanks, Enrique. > > El jueves, 2 de marzo de 2023

Re: [sage-devel] Re: XCode Update creates "C compiler cannot create executables"

I just ran into this error after upgrading to MacOS 13.3. I first started seeing issues with stdio.h being missing, so I tried reinstalling Xcode command line tools. I was then missing complex.h, so I tried reinstalling all of Xcode. Then configure gave me the error described in this thread; loo

Re: [sage-devel] bug in realfield when passing python integers

I don't think this is a bug that Sage can fix. When you execute RR(8059/9042) in Python, it first evaluates 8059/9042 which produces a float, then passes that to RR. There's no way for RR to know that you initially input a ratio of ints. David On Mon, Apr 10, 2023 at 4:11 PM aw wrote: > when p

Re: [sage-devel] RealField isn't doing it right

I agree with William that you should refrain from insulting the Sage developers, especially when the underlying problem comes from your misunderstanding of how floating point arithmetic works. To respond to the content of your message, finite precision real fields in Sage are implemented using flo

Re: [sage-devel] RealField isn't doing it right

On Mon, Apr 17, 2023 at 7:39 PM aw wrote: > On Monday, April 17, 2023 at 4:05:56 PM UTC-6 Nils Bruin wrote: > > But you WON'T be computing with exact quantities in RealField(200) unless > your number can be expressed as +- an unsigned 200-bit integer times a > power of two, so you're very fundam

Re: [sage-devel] RealField isn't doing it right

Did you read my message from last night? I highlighted exactly the problems with what you're suggesting. David On Tue, Apr 18, 2023 at 5:59 PM aw wrote: > On Tuesday, April 18, 2023 at 3:29:03 PM UTC-6 Dima Pasechnik wrote: > > It is a problem, as e^1.1 cannot be represented exactly, and it is

Re: [sage-devel] RealField isn't doing it right

On Tue, Apr 18, 2023 at 8:06 PM aw wrote: > On Tuesday, April 18, 2023 at 4:14:41 PM UTC-6 David Roe wrote: > > Did you read my message from last night? I highlighted exactly the > problems with what you're suggesting. > David > > > In that post you outlined some

Re: [sage-devel] RealField isn't doing it right

On Tue, Apr 18, 2023 at 8:15 PM aw wrote: > On Tuesday, April 18, 2023 at 4:19:45 PM UTC-6 Nils Bruin wrote: > > > It may not be the default, but you can still have it! As referenced > before, just execute upon startup: > > old_RealNumber=RealNumber > def RealNumber(*args, **kwargs): > return

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

On Wed, Apr 26, 2023 at 6:41 AM Dima Pasechnik wrote: > PS. I think openssl spkg should just be removed from Sage, it serves > no purpose as far as I can tell. > For a long time it was very important for getting a functional Sage on MacOS; is that no longer the case? David > > On Wed, Apr 26,

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

I'm sorry to have prompted another flame war, but please keep the tone polite Dima and Matthias. I know that you're both frustrated at this issue being unresolved, but it's not appropriate to have a fight like this that goes to 2570 different people's inboxes, with frequent emails sniping at each

Re: [sage-devel] cysignals/sig_on...sig_off

On Sun, Apr 30, 2023 at 10:49 AM 'jonatha...@googlemail.com' via sage-devel wrote: > Does cysignals get enough support to keep going or do we want to try a > different approach? This different approach will for sure not be as > efficient, but will probably need less effort to maintain. > sig_on/

Re: [sage-devel] cysignals/sig_on...sig_off

ments to mathematics interaction with the desired > organization "Oppia" within Web category. > > > > Let me know if you all sage developers want further information > regarding myself to search my result. > > Why are you spamming this group by posting several copies of the

Re: [sage-devel] Re: ping - please cast you vote: VOTE: Follow NEP 29: Recommended Python version

I will delete any messages to this thread in the next week. I encourage people who have not yet engaged to think about the issue and see if they have a compromise to suggest. David On Wed, May 31, 2023 at 5:24 PM G. M.-S. wrote: > > Hi all. > > I would like to ask for a moratorium of at least 1

Re: [sage-devel] Re: Why matrix powers are slower over Integers(p) than in ZZ?

The problem is that Sage doesn't have a specialized type for integers mod N: sage: type(M3) The best solution would be to create one, but of course that's a lot of work. Another possibility would be to change the __pow__ method for integer matrices to not ignore the modulus argument. As a worka

Re: [sage-devel] Modularization project: V. The blocs

I assume that the MANIFEST.in.m4 file contains a list of what's in each package, right? There's also sagemath-objects and sagemath-categories (are there any others?); can you send analogous links for those so that we can understand how the library is being broken up into pieces? Is every file par

Re: [sage-devel] Modularization project: V. The blocs

How do you handle files that depend on multiple libraries (like both FLINT and NTL for example)? Are these only included in sagemath-standard? David On Fri, Jun 16, 2023 at 2:19 PM Matthias Koeppe wrote: > On Friday, June 16, 2023 at 11:07:36 AM UTC-7 David Roe wrote: > > I assume

Re: [sage-devel] ping - please cast you vote: VOTE: Follow NEP 29: Recommended Python version

Thanks for restarting the discussion Tobias. From my perspective, there are several things that can move this conversation forward. 1. More clarity on how NEP-29 will be implemented in Sage. In particular, that policy just guarantees a particular time frame during which Python *will* be supported

Re: [sage-devel] Re: Voting: Block-scoped optional tag and the keyword

I vote for (A) On Thu, Jun 29, 2023 at 5:13 AM Eric Gourgoulhon wrote: > I vote for (A) > > -- > 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+unsub

Re: [sage-devel] How to make call to latex() not evaluate its content again?

Even if adding some assumptions makes this particular integral evaluate fully, the underlying problem may still show up in other cases. I haven't tracked it down fully (and probably won't spend more time on this), but the error messages are coming from Sage's interface to Giac, via this function i

Re: [sage-devel] Re: Issue with orders in number fields

If you want the order generated by a, you can do sage: K.=NumberField(x^2-10) sage: OK=K.maximal_order() sage: O = K.order(a) sage: O.index_in(OK) 1 Note that this correctly fails in Nils' example: sage: K.order(a^2) ... ValueError: the rank of the span of gens is wrong David On Thu, Sep 7, 202

Re: [sage-devel] remove log_html() and other log_*()

On Thu, Apr 30, 2020 at 2:56 PM Michael Orlitzky wrote: > On 4/30/20 2:10 PM, John H Palmieri wrote: > > > > > They're doctested, and they still work. What makes the implementation > > bad? They use standard Python library tools to walk a directory tree and > > then to do a regexp search on the f

Re: [sage-devel] Proposal for Sage 9.3: Modularization of sagelib; in particular, splitting out a sage_objects package

On Sun, May 3, 2020 at 8:27 PM Michael Orlitzky wrote: > > A good first step might be to ban new circular imports, but that means > that e.g. parent structures and their element classes would need to be > defined in the same files for things like > > class FooElement(...): > pass > > cl

Re: [sage-devel] Re: Newforms calculation is nondeterministic

As Kevin suggested, the fact that different defining polynomials are chosen is an artifact of the algorithm. Perhaps one could add a keyword argument to the newforms method that had it call polredabs on the field? Polredabs can be expensive in larger degree, so there should be an option to disabl

Re: [sage-devel] Re: Lie subalgebra implementation bug

On Tue, Sep 22, 2020 at 6:46 AM Alec Linden Disney-Hogg < disneyh...@gmail.com> wrote: > Hi Travis, > > Yes I just updated to 9.1 and have found this problem fixed, thanks. > > I'd love to contribute to sage, and indeed have ideas for Verma modules > that I'd like to see if it's possible to get to

Re: [sage-devel] UMBC Optimization seminar

For more online seminars see researchseminars.org, a site I created this spring with colleagues at MIT. There are currently 518 upcoming talks listed in math. Michael, if you know the organizers of your optimization seminar I would encourage them to add it to the site (you can have them contact m

Re: [sage-devel] Re: "Real Field" -> "Real Floating-point Field"

I agree with Nathan and Frédéric about backward compatibility. The original question was about whether to proceed with creating a GenuineRealField object. I'm in favor of progress in that direction! But I'd also like to see what that object looks like before making a decision about changing the

Re: [sage-devel] Obtain a lattice basis of a linear rational subspace

I think this should do what you need: sage: A = matrix([ : (1, 0, 0, 0, 1/10), : (0, 1, 0, 0, 1/10), : (0, 0, 1, 0, 1/10), : (0, 0, 0, 1, 1/10) : ]) sage: A = (A * A.denominator()).change_ring(ZZ) sage: A.saturation() [10 0 0 0 1] [-1 1 0 0 0] [-1 0 1 0 0]

Re: [sage-devel] Error while installing SAGE

It looks like you ran out of disk space. I would suggest making more room on your hard drive and trying again. I'm not sure exactly how much room Sage needs, but 8GB should be plenty. David On Tue, Nov 17, 2020 at 1:07 PM Rejani Rajesh wrote: > hello > > i had trouble installing the sage from

<    3   4   5   6   7   8   9   10   >