[sage-devel] Re: Build from source on Apple Silicon M3

[Trevor Karn]

Thanks Matthias! I can build off of commit a8a8dd875a

On Sunday, May 19, 2024 at 9:44:20 PM UTC-5 Matthias Koeppe wrote:

> You'll need:
> - https://github.com/sagemath/sage/pull/38025
> - https://github.com/sagemath/sage/pull/38008
> - https://github.com/sagemath/sage/pull/37919
> - https://github.com/sagemath/sage/pull/38021
>
> On Sunday, May 19, 2024 at 7:04:58 PM UTC-7 Trevor Karn wrote:
>
>> Hi all,
>>
>> I am trying to build from source on Apple Silicon M3. As predicted by 
>> several sources (below), `gfortran` fails to build on Apple Silicon. 
>>
>> After running `./configure` from SAGE_ROOT, I see the line:
>>
>> gfortran:   no suitable system package; standard, 
>> SPKG version 12.2.0 will be installed
>> Then when I `make`, the build fails with output:
>>
>>   [gfortran-12.2.0]   
>> 
>>
>>   [gfortran-12.2.0]   Error building gfortran-12.2.0
>>
>>   [gfortran-12.2.0]   
>> 
>>
>>   [gfortran-12.2.0]   
>>
>>   [gfortran-12.2.0]   real 0m49.588s
>>
>>   [gfortran-12.2.0]   user 2m35.894s
>>
>>   [gfortran-12.2.0]   sys 1m22.419s
>>
>>   [gfortran-12.2.0]   
>> 
>>
>>   [gfortran-12.2.0]   Error building package gfortran-12.2.0
>>
>>   [gfortran-12.2.0]   
>> 
>>
>> The following lines in config.log seems relevant:
>>
>> ## Checking whether SageMath should install SPKG gfortran... ##
>> configure:18136: checking the version of gfortran
>> configure:18172: Installing gfortran because gfortran is version 14, 
>> which is too recent for this version of Sage
>> configure:18206: no suitable system package found for SPKG gfortran
>> configure:18331: checking whether any of gfortran is installed as or will 
>> be installed as SPKG
>> configure:110356: result: gfortran:   no suitable 
>> system package; standard, SPKG version 12.2.0 will be installed
>>
>> Since the build wanted to install SPKG version 12.2.0 and thought 14 was 
>> "too recent for this version of Sage" I thought I would try `brew install 
>> gcc@12`, so that a "suitable system package" would be available. After 
>> running `./configure` again I still see 
>>
>> gfortran:   no suitable system package; standard, 
>> SPKG version 12.2.0 will be installed
>>
>> Then `make` fails again as predicted.
>>
>> How can I use either the homebrew gcc@12 or gcc@14 in the build process? 
>> Is this done by setting the `FC` environment variable? If so, to what value 
>> should I set it? (I tried FC=gcc@12, and still had the same problem.)
>>
>> Log files are attached.
>>
>> Thanks!
>>
>> -Trevor
>>
>> Sources predicting that `gfortran` installation will fail:
>> https://github.com/sagemath/sage/wiki/Sage-9.6-Release-Tour
>>
>> https://ask.sagemath.org/question/63142/cannot-build-sage-from-source-on-m1-mac/
>>
>> https://github.com/sagemath/sage/?tab=readme-ov-file#macos-preparing-the-platform
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/59fb06e0-a649-45aa-94a1-b1ba8c3dbc2fn%40googlegroups.com.

[sage-devel] Re: Application for NumFOCUS affiliation of SageMath

[Trevor Karn]

Will this thread be used for discussion prior to the April 15 deadline?

On Monday, January 15, 2024 at 11:42:10 PM UTC-8 Matthias Koeppe wrote:

> As I have not received sufficient feedback by today, I'll retarget to the 
> next deadline, Apr 15.
> Comments and discussion please by January 31.
>
>
>
> On Saturday, January 13, 2024 at 5:55:29 PM UTC-8 Matthias Koeppe wrote:
>
>> Over the years, it has been suggested that our project seek affiliation 
>> with the NumFocus organization (https://numfocus.org/)
>>
>> *2016:* E.M. Bray asks in 
>> https://groups.google.com/g/sage-devel/c/8-BfX8KxFuI/m/CQRmz_3vDQAJ:  Is 
>> there any particular objection about approaching NumFOCUS [...]? (there is 
>> no objection or any response for that matter)
>>
>> *2018: *E.M. Bray's 2018 sage-devel post (
>> https://groups.google.com/g/sage-devel/c/aY0GVqBwFkI/m/cTqfaBN5AQAJ) 
>> gives a great overview on benefits for us and the difference between 
>> "Affiliated projects" and "Sponsored projects"; in the same thread, D.V. 
>> Pasechnik reports having been put in charge of co-leading it by William, 
>> but notes his reservations about CoC; Jason Grout reports having given 
>> NumFOCUS people a heads-up.
>>
>> *2019:* V. Delecroix brings up NumFOCUS (
>> https://groups.google.com/g/sage-devel/c/sGFOYBeEq-Q/m/NUCfS2zhAQAJ), S. 
>> Lelievre points to the 2018 post, E.M. Bray follows up with a discussion of 
>> questions of governance.
>>
>> *2022:* D.V. Pasechnik notes that the NumFOCUS effort "appears to be 
>> stalled". 
>> https://groups.google.com/g/sage-devel/c/G7qZkzjWDZU/m/MgrEqTqJAQAJ
>>
>> *As of today, 2024,* in my opinion, SageMath is clearly not able to meet 
>> the additional requirements of a NumFOCUS Sponsored Project (
>> https://numfocus.org/projects-overview): "A transparent, publicly 
>> visible governance model" (), "A roadmap outlining high priority work 
>> areas" (although my modularization project provides 
>> https://github.com/sagemath/sage/issues/29705 provides a viable 
>> candidate for > 50% of it).
>>
>> *But we can easily apply to become a NumFOCUS Affiliated Project; it's 21 
>> easy questions in a slightly awkward web form (*
>> https://numfocus.typeform.com/to/VUPE35?typeform-source=numfocus.org)*. 
>> The next deadline is Monday January 15*, and I will turn in an 
>> application on behalf of the project unless I hear serious, qualified 
>> objections.
>>
>> Below are my draft responses to the 21 questions; any suggestions and 
>> corrections are very welcome.
>>
>> 
>> Question 1
>> Does your project have a contributor Code of Conduct?
>> *Yes*
>>
>> Question 2
>> What is the name of your project?
>>
>> *SageMath*
>> Question 3
>> Please provide the url of your project's (primary) repo:
>>
>> *https://github.com/sagemath/sage *
>> Question 4
>> Your project's website:
>>
>> *https://www.sagemath.org/ *
>> Question 5
>> Please provide a summary description of your project in a few sentences:
>> *Comprehensive mathematical software system*
>>
>> Question 6
>> Does your project have a logo?
>>
>> *Yes*
>>
>> Question 7
>> Please upload a .svg file of your project's logo. A "square" format is 
>> best.
>> *982721.png*
>>
>> Question 8
>> Your project's Twitter handle or other social media handles/urls:
>> *https://twitter.com/sagemath , 
>> https://mathstodon.xyz/@sagemath , *
>> *https://www.facebook.com/pages/Sage-Math/26593144945 
>> , *
>> Question 9
>> Why do you want your project to join NumFOCUS?
>> *TBD*
>>
>> Question 10
>> Are you applying for Fiscal Sponsorship or Affiliation? For more 
>> information, see https://numfocus.org/projects-overview
>>
>> *B. affiliation*
>> Question 11
>> How does your project relate to or integrate with the existing ecosystem 
>> of NumFOCUS tools?
>> *Cython, CVXpy, igraph, IPython, Jupyter, Matplotlib, NetworkX, NumPy, 
>> SciPy, SymPy are dependencies of SageMath. Additionally, volunteers 
>> maintain conda-forge packaging of SageMath.*
>>
>> Question 12
>> Describe how your project furthers the NumFOCUS mission: 
>> https://numfocus.org/community/mission
>> *SageMath is mathematical software with an integration mission. *
>>
>> Question 13
>> How many active contributors does your project currently have?
>>
>> *70*
>> Question 14
>> Any comments you’d like to make on the number of your active contributors:
>>
>> *as per 
>> https://github.com/sagemath/sage/graphs/contributors?from=2023-02-09=2024-01-13=c
>>  
>> *
>> Question 15
>> What is your project doing to attract and/or mentor new contributors and 
>> maintainers?
>>
>> *Organize virtual and in-person workshops, participate in Google Summer 
>> of Code*
>> Question 16
>> Where do you host conversations about project 

Re: [sage-devel] Re: f.g. subrings of polynomial rings and their Hilbert-Poincare series

[Trevor Karn]

If I understand correctly, Macaulay2 does this in the SubalgebraBases 
package: https://arxiv.org/abs/2302.12473 might provide inspiration?

On Tuesday, July 4, 2023 at 6:39:53 AM UTC-5 Dima Pasechnik wrote:

>
>
> On Tue, 4 Jul 2023, 12:26 Kwankyu Lee,  wrote:
>
>> Also, as far as I understand, Sage can compute the minimal free 
>> resolution of 
>> the module of syzygies of S, and from the resolution the presentation can 
>> be 
>> assembled.
>>
>>
>> Yes. It's here: 
>> https://doc.sagemath.org/html/en/reference/resolutions/index.html
>>
>> So it seems that the only missing bit is computation of a presentation of 
>> S.
>>
>>
>> Let phi: R[y_1,...,y_k] -> R[x_1,...,x_n] mapping by y_i -> f_i. Then, 
>> perhaps, your I is the kernel of phi.
>>
>
> Ah, right, thanks. I suppose resolutions are only needed for handling more 
> delicate properties of S, e.g. Cohen-Macauleyness, systems of parameters, 
> etc.
>
>
>
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/6f50eeb6-9611-4a09-ad4d-8fff20875cb9n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/e5eef2f3-e4be-465b-848a-8dbf8befe81fn%40googlegroups.com.

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

[Trevor Karn]

I don't have much understanding of how floating point arithmetic works, but 
the argument 

>If you're writing python code, you should expect 2*0.5 to return a
>float. But if you're learning linear algebra for the first time and
>typing a matrix into the Sage notebook, typing 0.5 instead of 1/2
>should not ruin the entire assignment without so much as a warning.

seems important to me. I also sometimes worry that Sage seems to be written 
for users who are both experts in [insert mathematical field here] and 
Python. This prevents (a) mathematical experts who don't know python from 
using Sage and (b) more junior students from using sage. Maybe one can make 
the argument that mathematical experts should just learn python (although I 
would disagree), but I think (b) is a genuine problem. Mathematica doesn't 
seem to require the user to be expert in either math or Wolfram language 
(or maybe I haven't used it enough). I don't have an actionable complaint 
here, but it is something I encounter when helping folks around my math 
department with their code. I'm trying to keep it in mind as I develop 
code. 

I see that

sage: A = matrix([[-3, 2, 1 ],[ 2,-4, 4 ], [ 1, 2,-5 ]])
sage: B = (2*0.5*A)
sage: rank(B)
3

What about floating point arithmetic makes this break? I print (B) and see 

[-3.00  2.00  1.00]
[ 2.00 -4.00  4.00]
[ 1.00  2.00 -5.00]

which doesn't have any obvious reason to be not rank-2. Could someone ELI5?

It is also not unprecedented for an error to be thrown for the rank method. 
>From the documentation:

  sage: m = matrix(Integers(4), 2, [2,2,2,2])

  sage: m.rank()

  Traceback (most recent call last):

  ...

  NotImplementedError: Echelon form not implemented over 'Ring of 
integers modulo 4'.

It seems reasonable to me that a similar NotImplementedError could be 
thrown for generic dense matrices. Is that an acceptable solution @Dima and 
@Michael? It seems easy enough to add a `.rank()` method in 
`matrix/matrix_generic_dense.pyx` which throws the error. I'd be happy to 
make this PR if that is reasonable to folks.
On Sunday, April 16, 2023 at 6:53:36 AM UTC-5 Dima Pasechnik wrote:

> On Sun, Apr 16, 2023 at 12:25 AM Michael Orlitzky  
> wrote:
> >
> > On Sat, 2023-04-15 at 18:20 -0400, David Roe wrote:
> > > 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.
> >
> > I was given this response many times, and I think it's condescending
> > (no offense). My favorite permabug:
> >
> > sage: A = matrix([[-3, 2, 1 ],
> > : [ 2,-4, 4 ],
> > : [ 1, 2,-5 ]])
> > sage: B = (2 * 0.5 * A)
> > sage: B == A
> > True
> > sage: B.rank() == A.rank()
> > False
> >
>
> that's a bug in B.rank() - in my book at least. It's perfectly
> possible to either reliably derive that rank(B)=2,
> as far as it makes sense in the given precision, or throw an error.
> It's just not implemented.
>
>
> > I promise you that I know what a floating point number is, and that
> > they aren't the problem. The problem is that reasonable expectations
> > are not met by the Sage user interface. It shouldn't be that easy to
> > get the computer to lie to me. An explanation is of course possible,
> > but only after the fact, and only with a level of knowledge about the
> > preprocessor that is beyond most users.
> >
> > --
> > 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+...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/c8531f5211ebfe590ed2b38390b33ef26df1d1eb.camel%40orlitzky.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/cc5a27a3-e855-43e1-a494-b411c613497dn%40googlegroups.com.

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

[Trevor Karn]

Ok so my takeaway is that for now at least we treat all PRs that are
untagged as needs review. Is there a way to set as a default or get a bot
to automatically apply just the needs review label to any new PR?

On Sat, Feb 25, 2023 at 2:20 PM Matthias Koeppe 
wrote:

> Re the "needs review" tag, see earlier discussion in
> https://github.com/sagemath/trac-to-github/issues/8#issuecomment-1367744734
>
>
> On Saturday, February 25, 2023 at 11:48:08 AM UTC-8 Vincent Delecroix
> wrote:
>
>> I think that the needs_review positive_review tags do not fit well in
>> the github workflow. These have been kept to mimic the trac workflow
>> but are annoying. I support Edgar suggestion that the "needs review
>> tag" should be replaced by "not a draft" status. Similarly, the
>> "positive review tag" would better be replaced by something like
>> "approved by a developer".
>>
>> On Sat, 25 Feb 2023 at 20:38, Edgar Costa  wrote:
>> >
>> > Most likely not the status quo at the moment, but if a PR is not ready
>> to be reviewed should be marked as a draft, which the author can do without
>> any special permissions.
>> > Otherwise, I would assume the PR is ready to be reviewed.
>> >
>> > On Fri, Feb 24, 2023 at 9:43 PM Trevor Karn 
>> wrote:
>> >>
>> >> How do new developers tag their PR as "needs review" without having
>> triage access?
>> >>
>> >> On Thursday, February 23, 2023 at 1:37:07 AM UTC-6 David Roe wrote:
>> >>>
>> >>> 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 and marking as duplicate. I'm fine with giving these permissions
>> to people after their first PR is merged, but some might argue for more of
>> a history with contributors.
>> >>>
>> >>> Julian and I had talked about writing a bot to handle these
>> permissions, but haven't gotten around to it yet.
>> >>> David
>> >>>
>> >>> On Thu, Feb 23, 2023 at 5:33 AM Kwankyu Lee 
>> wrote:
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> We are getting PRs from non-member contributors.
>> >>>>
>> >>>> What is the procedure or the condition to be invited for membership?
>> >>>>
>> >>>> --
>> >>>> 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+...@googlegroups.com.
>> >>>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/9eae5420-6b43-440e-b36d-d30c3b23421bn%40googlegroups.com.
>>
>> >>
>> >> --
>> >> 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+...@googlegroups.com.
>> >> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/1ee1ac47-44bb-4c0d-a8df-132fc4cdc86an%40googlegroups.com.
>>
>> >
>> > --
>> > 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+...@googlegroups.com.
>> > To view this discussion on the web visit
>> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x7fGhOaaHwy3DEyfC%3DomQYV1c8JWCkanEcCRUdo7bFCHw%40mail.gmail.com.
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/Zos8buxIDU4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/e6773a76-9236-45b6-97da-b15fe6af1860n%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-devel/e6773a76-9236-45b6-97da-b15fe6af1860n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
-- 
Best,

Trevor

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAJ6VCMA%3DbHame4D3hoJEB2T9fx%2BT-DvWoRqf2rD_39hvW66NRg%40mail.gmail.com.

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

[Trevor Karn]

How do new developers tag their PR as "needs review" without having triage 
access?

On Thursday, February 23, 2023 at 1:37:07 AM UTC-6 David Roe wrote:

> 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 and marking as duplicate.  I'm fine with giving these 
> permissions to people after their first PR is merged, but some might argue 
> for more of a history with contributors.
>
> Julian and I had talked about writing a bot to handle these permissions, 
> but haven't gotten around to it yet.
> David
>
> On Thu, Feb 23, 2023 at 5:33 AM Kwankyu Lee  wrote:
>
>> Hi,
>>
>> We are getting PRs from non-member contributors.
>>
>> What is the procedure or the condition to be invited for membership?
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/9eae5420-6b43-440e-b36d-d30c3b23421bn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1ee1ac47-44bb-4c0d-a8df-132fc4cdc86an%40googlegroups.com.

[sage-devel] Re: pull requests for migrated issues

[Trevor Karn]

I could also not add labels.

On Monday, February 6, 2023 at 4:44:03 AM UTC-6 axio...@yahoo.de wrote:

> I just opened an issue (the first on github?), but I could not add labels 
> either.  Perhaps the labels are deactivated for ordinary users?
>
> On Monday, 6 February 2023 at 10:00:52 UTC+1 Kwankyu Lee wrote:
>
>> On Monday, February 6, 2023 at 5:47:22 PM UTC+9 Lorenz Panny wrote:
>> Sorry if this is answered somewhere in the new documentation, I couldn't 
>> find it: What is the intended procedure for migrated issues which were in 
>> "needs review" state and already had a branch? Am I to push the branch to 
>> my own fork and create a fresh pull request for each such issue?
>>
>> Yes, according to the guide: 
>>
>>
>> https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md#for-contributing-a-change-that-addresses-an-existing-open-issue-that-has-been-migrated-from-trac
>>
>>  But the procedure is not smooth yet. I could not add labels to 
>>
>> https://github.com/sagemath/sage/pull/34960
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/298b2ef2-765f-4110-9b54-25311da1f27cn%40googlegroups.com.

[sage-devel] Automorphism group of a PermutationGroup without GAP directly

[Trevor Karn]

Am I correctly understanding that there is currently no method to return 
the automorphism group of PermutationGroup without directly invoking GAP? 
I'm thinking something along the lines of the `AbelianGroupGap.aut()` 
method. It doesn't seem to bad to add, I just want to make sure I'm not 
missing something before opening a ticket.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/3c0c6840-3cdb-429d-8e89-ef4acafe3ff4n%40googlegroups.com.

Re: [sage-devel] Re: Bug in poset

[Trevor Karn]

Thanks Dima. I certainly agree that there is a mathematical error with my
approach. I'm wondering if there is still a bug since the result of
compare(x,y) and P.islequal(x,y) differ. Shouldn't they be the same, even
if I am giving them bad input?

Best Regards,

Trevor Karn


On Thu, Jan 12, 2023 at 5:52 AM Dima Pasechnik  wrote:

> No, no bug (yet).
>
> The problem is that you are not careful constructing the correct subgroups
> to use.
> E.g. if you want groups[2] to be a subgroup of groups[5]=<(1,2,3,4)>
> you must take groups[2]=<(1,3)(2,4)>, not groups[2]=<(1,2)(3,4)>.
> You can start with the maximal subgroups of S_5, and intersect them, then
> intersect the intersections, etc.
>
> Or you can rewrite your compare(a,b) in terms of "an element of the
> conjugacy class of subgroups with `b`
> a representative contained in `a`"
> E.g. using libgap:
>
> sage:
> groups[-1]._libgap_().ConjugacyClassSubgroups(groups[1]._libgap_()).Elements()
> [ Group([ (4,5) ]), Group([ (3,4) ]), Group([ (3,5) ]), Group([ (2,3) ]),
> Group([ (2,4) ]), Group([ (2,5) ]), Group([ (1,2) ]), Group([ (1,3) ]),
> Group([ (1,4) ]), Group([ (1,5) ]) ]
>
> But this might well be a different poset, as once you fixed just one
> maximal subgroup H_1, the conjugacy class of the 2nd maximal subgroup H_2
> might already be splitting into different orbits w.r.t. conjugaction by
> H_1, so potentially different choices, etc...
>
> HTH
> Dima
>
>
> On Wednesday, January 11, 2023 at 6:30:32 PM UTC dmo...@deductivepress.ca
> wrote:
>
>> P erroneously thinks that GA(1,5) is less than A5.  I have no idea what's
>> causing that either.
>>
>> On Wednesday, January 11, 2023 at 11:21:39 AM UTC-7 Trevor Karn wrote:
>>
>>> Thanks for the confirmation. I'll double check this is not a logic bug
>>> before I open a ticket.
>>>
>>> On Wednesday, January 11, 2023 at 1:20:09 PM UTC-5 Trevor Karn wrote:
>>>
>>>> At least part of the problem is that I gave bad generators for GA(1,5).
>>>> It should be [[(1,2,3,4,5)],[(2,3,5,4)]].
>>>>
>>>> On Wednesday, January 11, 2023 at 11:58:32 AM UTC-5 Trevor Karn wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I was wondering if anyone can reproduce this bug with Poset creation.
>>>>> I create a Poset by passing the elements and the comparison function as a
>>>>> tuple (elements, func) and a pair of elements for which func(x,y) returns
>>>>> True has P.lequal(x,y) returning False
>>>>>
>>>>> I'm trying to create the subgroup lattice up to conjugacy of S5.
>>>>>
>>>>> sage: load('s5-subgroup.sage')  # builds poset, see below
>>>>> sage: groups[-2]
>>>>> Permutation Group with generators [(1,2,3), (1,2,3,4,5)]
>>>>> sage: groups[-1]
>>>>> Permutation Group with generators [(1,2), (1,2,3,4,5)]
>>>>> sage: compare(groups[-2], groups[-1])
>>>>> True
>>>>> sage: P.is_lequal('A5','S5')
>>>>> False
>>>>>
>>>>> The content of 's5-subgroup.sage' is below.
>>>>>
>>>>> gens = [
>>>>> [[]],  # trivial
>>>>> [[(1,2)]],  # S2
>>>>> [[(1,2),(3,4)]],  #z/2
>>>>> [[(1,2)],[(3,4)]],  # disjoint V4
>>>>> [[(1,2),(3,4)],[(1,3),(2,4)]],  # double transp V4
>>>>> [[(1,2,3,4)]],  # z/4
>>>>> [[(1,2,3,4)],[(1,3)]],  # D8 (D4 in GAP notation)
>>>>> [[(1,2,3)]],  # z/3
>>>>> [[(1,2,3)],[(4,5)]],  # z/6
>>>>> [[(1,2,3)],[(1,2)]],  # S3
>>>>> [[(1,2,3)],[(1,2),(4,5)]],  # twisted S3
>>>>> [[(1,2,3)],[(1,2)],[(4,5)]],  # S3 x S2
>>>>> [[(1,2),(3,4)],[(1,2,3)]],  # A4
>>>>> [[(1,2,3,4)],[(1,2)]],  # S4
>>>>> [[(1,2,3,4,5)]],  # z/5
>>>>> [[(1,2,3,4,5)],[(2,5),(3,4)]],  # D10
>>>>> [[(1,2,3,4,5)],[(2,3,4,5)]],  # GA(1,5)
>>>>> [[(1,2,3,4,5)],[(1,2,3)]],  # A5
>>>>> [[(1,2,3,4,5)],[(1,2)]]  # S5
>>>>> ];
>>>>>
>>>>> strs = ['1', 'S2', 'Z/2', 'V4', 'V4 (dbl)', 'Z/4', 'D8',
>>>>> 'Z/3', 'Z/6', 'S3', 'S3 (twist)', 'S3xS2',
>>>>> 'A4', 'S4', 'Z/5', 'D10', 'GA(1,5)', 'A5',
>>>>> 'S5']
>>>>>
>>>>> to_group = lamb

[sage-devel] Re: Bug in poset

[Trevor Karn]

Thanks for the confirmation. I'll double check this is not a logic bug 
before I open a ticket.

On Wednesday, January 11, 2023 at 1:20:09 PM UTC-5 Trevor Karn wrote:

> At least part of the problem is that I gave bad generators for GA(1,5). It 
> should be [[(1,2,3,4,5)],[(2,3,5,4)]].
>
> On Wednesday, January 11, 2023 at 11:58:32 AM UTC-5 Trevor Karn wrote:
>
>> Hi all,
>>
>> I was wondering if anyone can reproduce this bug with Poset creation. I 
>> create a Poset by passing the elements and the comparison function as a 
>> tuple (elements, func) and a pair of elements for which func(x,y) returns 
>> True has P.lequal(x,y) returning False
>>
>> I'm trying to create the subgroup lattice up to conjugacy of S5.
>>
>> sage: load('s5-subgroup.sage')  # builds poset, see below
>> sage: groups[-2]
>> Permutation Group with generators [(1,2,3), (1,2,3,4,5)]
>> sage: groups[-1]
>> Permutation Group with generators [(1,2), (1,2,3,4,5)]
>> sage: compare(groups[-2], groups[-1])
>> True
>> sage: P.is_lequal('A5','S5')
>> False
>>
>> The content of 's5-subgroup.sage' is below.
>>
>> gens = [
>> [[]],  # trivial
>> [[(1,2)]],  # S2
>> [[(1,2),(3,4)]],  #z/2
>> [[(1,2)],[(3,4)]],  # disjoint V4
>> [[(1,2),(3,4)],[(1,3),(2,4)]],  # double transp V4
>> [[(1,2,3,4)]],  # z/4
>> [[(1,2,3,4)],[(1,3)]],  # D8 (D4 in GAP notation)
>> [[(1,2,3)]],  # z/3
>> [[(1,2,3)],[(4,5)]],  # z/6
>> [[(1,2,3)],[(1,2)]],  # S3
>> [[(1,2,3)],[(1,2),(4,5)]],  # twisted S3
>> [[(1,2,3)],[(1,2)],[(4,5)]],  # S3 x S2
>> [[(1,2),(3,4)],[(1,2,3)]],  # A4
>> [[(1,2,3,4)],[(1,2)]],  # S4
>> [[(1,2,3,4,5)]],  # z/5
>> [[(1,2,3,4,5)],[(2,5),(3,4)]],  # D10
>> [[(1,2,3,4,5)],[(2,3,4,5)]],  # GA(1,5)
>> [[(1,2,3,4,5)],[(1,2,3)]],  # A5
>> [[(1,2,3,4,5)],[(1,2)]]  # S5
>> ];
>>
>> strs = ['1', 'S2', 'Z/2', 'V4', 'V4 (dbl)', 'Z/4', 'D8', 
>> 'Z/3', 'Z/6', 'S3', 'S3 (twist)', 'S3xS2',
>> 'A4', 'S4', 'Z/5', 'D10', 'GA(1,5)', 'A5',
>> 'S5']
>>
>> to_group = lambda x: PermutationGroup(gens=x);
>> groups = list(map(to_group, gens));
>> compare = lambda x, y: x.is_subgroup(y);
>> P = Poset(data=(groups, compare), element_labels=strs)
>>
>>
>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/af1c187c-7a47-4698-99b5-4c4cdb1de9e8n%40googlegroups.com.

[sage-devel] Re: Bug in poset

[Trevor Karn]

At least part of the problem is that I gave bad generators for GA(1,5). It 
should be [[(1,2,3,4,5)],[(2,3,5,4)]].

On Wednesday, January 11, 2023 at 11:58:32 AM UTC-5 Trevor Karn wrote:

> Hi all,
>
> I was wondering if anyone can reproduce this bug with Poset creation. I 
> create a Poset by passing the elements and the comparison function as a 
> tuple (elements, func) and a pair of elements for which func(x,y) returns 
> True has P.lequal(x,y) returning False
>
> I'm trying to create the subgroup lattice up to conjugacy of S5.
>
> sage: load('s5-subgroup.sage')  # builds poset, see below
> sage: groups[-2]
> Permutation Group with generators [(1,2,3), (1,2,3,4,5)]
> sage: groups[-1]
> Permutation Group with generators [(1,2), (1,2,3,4,5)]
> sage: compare(groups[-2], groups[-1])
> True
> sage: P.is_lequal('A5','S5')
> False
>
> The content of 's5-subgroup.sage' is below.
>
> gens = [
> [[]],  # trivial
> [[(1,2)]],  # S2
> [[(1,2),(3,4)]],  #z/2
> [[(1,2)],[(3,4)]],  # disjoint V4
> [[(1,2),(3,4)],[(1,3),(2,4)]],  # double transp V4
> [[(1,2,3,4)]],  # z/4
> [[(1,2,3,4)],[(1,3)]],  # D8 (D4 in GAP notation)
> [[(1,2,3)]],  # z/3
> [[(1,2,3)],[(4,5)]],  # z/6
> [[(1,2,3)],[(1,2)]],  # S3
> [[(1,2,3)],[(1,2),(4,5)]],  # twisted S3
> [[(1,2,3)],[(1,2)],[(4,5)]],  # S3 x S2
> [[(1,2),(3,4)],[(1,2,3)]],  # A4
> [[(1,2,3,4)],[(1,2)]],  # S4
> [[(1,2,3,4,5)]],  # z/5
> [[(1,2,3,4,5)],[(2,5),(3,4)]],  # D10
> [[(1,2,3,4,5)],[(2,3,4,5)]],  # GA(1,5)
> [[(1,2,3,4,5)],[(1,2,3)]],  # A5
> [[(1,2,3,4,5)],[(1,2)]]  # S5
> ];
>
> strs = ['1', 'S2', 'Z/2', 'V4', 'V4 (dbl)', 'Z/4', 'D8', 
> 'Z/3', 'Z/6', 'S3', 'S3 (twist)', 'S3xS2',
> 'A4', 'S4', 'Z/5', 'D10', 'GA(1,5)', 'A5',
> 'S5']
>
> to_group = lambda x: PermutationGroup(gens=x);
> groups = list(map(to_group, gens));
> compare = lambda x, y: x.is_subgroup(y);
> P = Poset(data=(groups, compare), element_labels=strs)
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6f5df6f1-36ea-4ce0-ab82-43381a8736can%40googlegroups.com.

[sage-devel] Bug in poset

[Trevor Karn]

Hi all,

I was wondering if anyone can reproduce this bug with Poset creation. I 
create a Poset by passing the elements and the comparison function as a 
tuple (elements, func) and a pair of elements for which func(x,y) returns 
True has P.lequal(x,y) returning False

I'm trying to create the subgroup lattice up to conjugacy of S5.

sage: load('s5-subgroup.sage')  # builds poset, see below
sage: groups[-2]
Permutation Group with generators [(1,2,3), (1,2,3,4,5)]
sage: groups[-1]
Permutation Group with generators [(1,2), (1,2,3,4,5)]
sage: compare(groups[-2], groups[-1])
True
sage: P.is_lequal('A5','S5')
False

The content of 's5-subgroup.sage' is below.

gens = [
[[]],  # trivial
[[(1,2)]],  # S2
[[(1,2),(3,4)]],  #z/2
[[(1,2)],[(3,4)]],  # disjoint V4
[[(1,2),(3,4)],[(1,3),(2,4)]],  # double transp V4
[[(1,2,3,4)]],  # z/4
[[(1,2,3,4)],[(1,3)]],  # D8 (D4 in GAP notation)
[[(1,2,3)]],  # z/3
[[(1,2,3)],[(4,5)]],  # z/6
[[(1,2,3)],[(1,2)]],  # S3
[[(1,2,3)],[(1,2),(4,5)]],  # twisted S3
[[(1,2,3)],[(1,2)],[(4,5)]],  # S3 x S2
[[(1,2),(3,4)],[(1,2,3)]],  # A4
[[(1,2,3,4)],[(1,2)]],  # S4
[[(1,2,3,4,5)]],  # z/5
[[(1,2,3,4,5)],[(2,5),(3,4)]],  # D10
[[(1,2,3,4,5)],[(2,3,4,5)]],  # GA(1,5)
[[(1,2,3,4,5)],[(1,2,3)]],  # A5
[[(1,2,3,4,5)],[(1,2)]]  # S5
];

strs = ['1', 'S2', 'Z/2', 'V4', 'V4 (dbl)', 'Z/4', 'D8', 
'Z/3', 'Z/6', 'S3', 'S3 (twist)', 'S3xS2',
'A4', 'S4', 'Z/5', 'D10', 'GA(1,5)', 'A5',
'S5']

to_group = lambda x: PermutationGroup(gens=x);
groups = list(map(to_group, gens));
compare = lambda x, y: x.is_subgroup(y);
P = Poset(data=(groups, compare), element_labels=strs)



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/66ae93d6-fab5-46b7-84d7-e5ffd48010abn%40googlegroups.com.

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

[Trevor Karn]

+1 for Github

On Wednesday, September 21, 2022 at 12:57:43 PM UTC-5 Matthias Koeppe wrote:

> +1 for Github
>
> On Wednesday, September 21, 2022 at 10:23:36 AM UTC-7 David Roe wrote:
>
>> Dear Sage developers,
>> Following extensive discussion, both recently 
>>  
>> (prompted 
>> by issues upgrading the trac server) and over 
>>  the 
>>  
>> last 
>>  
>> decade 
>> , 
>> we are calling a vote on switching Sage development from Trac 
>>  to Github .  We've 
>> created a summary of the pros and cons of each system 
>> , a 
>> description 
>> of the development model to be used on github 
>> , 
>> and a trac ticket  for 
>> coordinating work on the transition.  More work will need to be done to 
>> carry out the actual transition once voting is complete.
>>
>> The voting will last until noon Eastern time (16:00 UTC) on Wednesday, 
>> October 5.  Please use this thread only for sending votes, to make it 
>> easier to count them afterward; there is a parallel thread where you can 
>> make arguments in favor of either system.
>>
>> Finally, I will close with a plea to be involved in this vote and 
>> discussion even if you are not a core Sage developer.  By definition, core 
>> Sage developers have become comfortable with trac, and I think that one of 
>> the major arguments in favor of github is that it will help bring in new 
>> contributors who are not familiar with Sage's development workfow 
>> .  Anyone who has 
>> ever contributed to the Sage code base or who maintains a Sage user package 
>> is welcome to vote.
>> David
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f494cb2c-3939-42ef-889b-12c9b0b1f791n%40googlegroups.com.

[sage-devel] Re: fractions of symmetric functions

[Trevor Karn]

As a workaround, does

R. = InfinitePolynomialRing(ZZ)
K = FractionField(R)
e[1]*e[7]^2/e[2] in K

where e[i] is the ith elementary symmetric function work? (Using the 
fundamental theorem of symmetric functions.) If you need to convert into a 
different basis you could then do that manually.

On Tuesday, August 9, 2022 at 12:14:01 PM UTC-7 axio...@yahoo.de wrote:

> I am guessing that part of the problem is
>
> sage: SymmetricFunctions(ZZ) in IntegralDomains()
> False
>
> The other problem is that fraction_field is not a parent method of 
> IntegralDomains.
>
> I'd be grateful for input / corrections.
>
> Martin
>
> On Tuesday, 9 August 2022 at 10:59:50 UTC+2 Martin R wrote:
>
>> I may be missing something, but sage doesn't let me do
>>
>> sage: R = SymmetricFunctions(QQ).e()
>> sage: FractionField(R)
>>
>> Naively, I would have thought that this makes sense.  Doesn't it?
>>
>> 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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/d109bb7a-dd9f-4315-a0c9-255844001be2n%40googlegroups.com.

[sage-devel] Re: Group algebra bug

[Trevor Karn]

Sorry of course the parent of kH(a) and kH.one() are the same. We do see 
that the parents of the indexing elements are different despite being 
mathematically the same:

sage: a.parent()
sage: list(kH.one().monomial_coefficients())[0].parent()
Permutation Group with generators [(5,6,7)(12,14,18), (1,2)(3,4)]
Permutation Group with generators [(5,6,7)(12,14,18), (1,2)(3,4)]
sage: list(kH.one().monomial_coefficients())[0].parent() is a.parent()
False

On Saturday, August 6, 2022 at 11:53:03 AM UTC-7 Trevor Karn wrote:

> The following bug was reported on sage-support, which I was able to 
> reproduce on 9.7.beta7.
>
> sage: H = PermutationGroup([[(1,2), (3,4)], [(5,6,7),(12,14,18)]])
> sage: kH = H.algebra(GF(2))
> sage: H.gens()
> ((5,6,7)(12,14,18), (1,2)(3,4))
> sage: a, b = H.gens()
> sage: x = kH(a) + kH(b) + kH.one(); x
> (5,6,7)(12,14,18) + (1,2)(3,4) + ()
> sage: x*x
> Traceback (most recent call last):
> ...
> RuntimeError: There is a bug in the coercion code in Sage.
> Both x (=()) and y (=(5,6,7)(12,14,18)) are supposed to have identical 
> parents but they don't.
> In fact, x has parent 'Permutation Group with generators 
> [(5,6,7)(12,14,18), (1,2)(3,4)]'
> whereas y has parent 'Permutation Group with generators 
> [(5,6,7)(12,14,18), (1,2)(3,4)]'
> Original elements () (parent Permutation Group with generators 
> [(5,6,7)(12,14,18), (1,2)(3,4)]) and (5,6,7)(12,14,18) (parent Permutation 
> Group with generators [(5,6,7)(12,14,18), (1,2)(3,4)]) and maps
>  None
>  (map 
> internal to coercion system -- copy before use)
> Coercion map:
>   From: Permutation Group with generators [(5,6,7)(12,14,18), (1,2)(3,4)]
>   To:   Permutation Group with generators [(5,6,7)(12,14,18), (1,2)(3,4)]
>
> I'm confused about why this is happening because
>
> sage: kH(a).parent()
> Algebra of Permutation Group with generators [(5,6,7)(12,14,18), 
> (1,2)(3,4)] over Finite Field of size 2
> sage: kH.one().parent()
> Algebra of Permutation Group with generators [(5,6,7)(12,14,18), 
> (1,2)(3,4)] over Finite Field of size 2
> sage: kH(a).parent() is kH.one().parent()
> True
>
> which I would think should mean that the condition on line 1323 of 
> sage/src/sage/structure/coerce.pyx that the parents are the same should be 
> tripped, but for some reason, it is not. I printed the hash of the parents 
> right before the bug (added it in between lines 1322 and 1323)  and they 
> have the same hash (547464660303730434), so I am surprised that they are 
> not considered the same. They are however recognized to be equal, and so 
> the elif statment checking if they are equal (on line 1327) is triggered, 
> but then the coercion of y_elt to parent(x_elt) on line 1329 seems to fail, 
> so that the parent comparison on 1330 still fails, kicking it out to the 
> coercion error.
>
> I'm unsure how to fix this but am willing to do the legwork to fix it if 
> anyone can explain the problem. 
>
> Opening https://trac.sagemath.org/ticket/34292.
>
>
> Full traceback:
>
> sage: H = PermutationGroup([[(*1*,*2*), (*3*,*4*)], [(*5*,*6*,*7*),(*12*,
> *14*,*18*)]])
>
> sage: kH = H.algebra(GF(*2*))
>
> sage: H.gens()
>
> ((5,6,7)(12,14,18), (1,2)(3,4))
>
> sage: a, b = H.gens()
>
> sage: x = kH(a) + kH(b) + kH.one(); x
>
> (5,6,7)(12,14,18) + (1,2)(3,4) + ()
>
> sage: x*x
>
> ---
>
> RuntimeError  Traceback (most recent call last)
>
> Input In [7], in ()
>
> > 1 x*x
>
>
> File ~/Applications/sage/src/sage/structure/element.pyx:1514, in 
> sage.structure.element.Element.__mul__()
>
> *   1512* cdef int cl = classify_elements(left, right)
>
> *   1513* if HAVE_SAME_PARENT(cl):
>
> -> 1514 return (left)._mul_(right)
>
> *   1515* if BOTH_ARE_ELEMENT(cl):
>
> *   1516* return coercion_model.bin_op(left, right, mul)
>
>
> File ~/Applications/sage/src/sage/structure/element.pyx:1560, in 
> sage.structure.element.Element._mul_()
>
> *   1558* raise bin_op_exception('*', self, other)
>
> *   1559* else:
>
> -> 1560 return python_op(other)
>
> *   1561* 
>
> *   1562* cdef _mul_long(self, long n):
>
>
> File ~/Applications/sage/src/sage/categories/coercion_methods.pyx:53, in 
> sage.categories.coercion_methods._mul_parent()
>
> * 51* True
>
> * 52* """
>
> ---> 53 return (self)._parent.product(self, other)
>
>
> File ~/Applications/sage/src/sage/categories/magmatic_algebras.py:215, in 
> MagmaticAlgebras.WithBasis.ParentMethods._product_from_product_on_basis_multiply(self,
>  
> left, right)
>
>

[sage-devel] Group algebra bug

[Trevor Karn]

The following bug was reported on sage-support, which I was able to 
reproduce on 9.7.beta7.

sage: H = PermutationGroup([[(1,2), (3,4)], [(5,6,7),(12,14,18)]])
sage: kH = H.algebra(GF(2))
sage: H.gens()
((5,6,7)(12,14,18), (1,2)(3,4))
sage: a, b = H.gens()
sage: x = kH(a) + kH(b) + kH.one(); x
(5,6,7)(12,14,18) + (1,2)(3,4) + ()
sage: x*x
Traceback (most recent call last):
...
RuntimeError: There is a bug in the coercion code in Sage.
Both x (=()) and y (=(5,6,7)(12,14,18)) are supposed to have identical 
parents but they don't.
In fact, x has parent 'Permutation Group with generators 
[(5,6,7)(12,14,18), (1,2)(3,4)]'
whereas y has parent 'Permutation Group with generators [(5,6,7)(12,14,18), 
(1,2)(3,4)]'
Original elements () (parent Permutation Group with generators 
[(5,6,7)(12,14,18), (1,2)(3,4)]) and (5,6,7)(12,14,18) (parent Permutation 
Group with generators [(5,6,7)(12,14,18), (1,2)(3,4)]) and maps
 None
 (map internal 
to coercion system -- copy before use)
Coercion map:
  From: Permutation Group with generators [(5,6,7)(12,14,18), (1,2)(3,4)]
  To:   Permutation Group with generators [(5,6,7)(12,14,18), (1,2)(3,4)]

I'm confused about why this is happening because

sage: kH(a).parent()
Algebra of Permutation Group with generators [(5,6,7)(12,14,18), 
(1,2)(3,4)] over Finite Field of size 2
sage: kH.one().parent()
Algebra of Permutation Group with generators [(5,6,7)(12,14,18), 
(1,2)(3,4)] over Finite Field of size 2
sage: kH(a).parent() is kH.one().parent()
True

which I would think should mean that the condition on line 1323 of 
sage/src/sage/structure/coerce.pyx that the parents are the same should be 
tripped, but for some reason, it is not. I printed the hash of the parents 
right before the bug (added it in between lines 1322 and 1323)  and they 
have the same hash (547464660303730434), so I am surprised that they are 
not considered the same. They are however recognized to be equal, and so 
the elif statment checking if they are equal (on line 1327) is triggered, 
but then the coercion of y_elt to parent(x_elt) on line 1329 seems to fail, 
so that the parent comparison on 1330 still fails, kicking it out to the 
coercion error.

I'm unsure how to fix this but am willing to do the legwork to fix it if 
anyone can explain the problem. 

Opening https://trac.sagemath.org/ticket/34292.


Full traceback:

sage: H = PermutationGroup([[(*1*,*2*), (*3*,*4*)], [(*5*,*6*,*7*),(*12*,
*14*,*18*)]])

sage: kH = H.algebra(GF(*2*))

sage: H.gens()

((5,6,7)(12,14,18), (1,2)(3,4))

sage: a, b = H.gens()

sage: x = kH(a) + kH(b) + kH.one(); x

(5,6,7)(12,14,18) + (1,2)(3,4) + ()

sage: x*x

---

RuntimeError  Traceback (most recent call last)

Input In [7], in ()

> 1 x*x


File ~/Applications/sage/src/sage/structure/element.pyx:1514, in 
sage.structure.element.Element.__mul__()

*   1512* cdef int cl = classify_elements(left, right)

*   1513* if HAVE_SAME_PARENT(cl):

-> 1514 return (left)._mul_(right)

*   1515* if BOTH_ARE_ELEMENT(cl):

*   1516* return coercion_model.bin_op(left, right, mul)


File ~/Applications/sage/src/sage/structure/element.pyx:1560, in 
sage.structure.element.Element._mul_()

*   1558* raise bin_op_exception('*', self, other)

*   1559* else:

-> 1560 return python_op(other)

*   1561* 

*   1562* cdef _mul_long(self, long n):


File ~/Applications/sage/src/sage/categories/coercion_methods.pyx:53, in 
sage.categories.coercion_methods._mul_parent()

* 51* True

* 52* """

---> 53 return (self)._parent.product(self, other)


File ~/Applications/sage/src/sage/categories/magmatic_algebras.py:215, in 
MagmaticAlgebras.WithBasis.ParentMethods._product_from_product_on_basis_multiply(self,
 
left, right)

*201* *def* _product_from_product_on_basis_multiply( self, left, right 
):

*202* r*"""*

*203* *Compute the product of two elements by extending*

*204* *bilinearly the method :meth:`product_on_basis`.*

   (...)

*213* 

*214* *"""*

--> 215 *return* self.linear_combination((self.product_on_basis(mon_left, 
mon_right), coeff_left * coeff_right )

*216* *for* (mon_left, coeff_left) 
*in* left.monomial_coefficients().items()

*217* *for* (mon_right, 
coeff_right) *in* right.monomial_coefficients().items() )


File ~/Applications/sage/src/sage/combinat/free_module.py:969, in 
CombinatorialFreeModule.linear_combination(self, iter_of_elements_coeff, 
factor_on_left)

*945* *def* linear_combination(self, iter_of_elements_coeff, 
factor_on_left=*True*):

*946* r*"""*

*947* *Return the linear combination `\lambda_1 v_1 + \cdots +*

*948* *\lambda_k v_k` (resp.  the linear combination `v_1 \lambda_1 
+*

   (...)

*967* *20*B[1] + 20*B[2]*

*968* *"""*

--> 969 *return* 

[sage-devel] Error in matrix reduction

[Trevor Karn]

Hi all,

I'm working on trac ticket https://trac.sagemath.org/ticket/34138 and 
during some testing on commit b3ef1f7 got an error that I don't understand. 
In implementing the F4 algorithm there is a computation of matrix RREF. 
During that step, on the "gametwo7" example 
of 
https://web.archive.org/web/20181129231728/http://www.cecm.sfu.ca/~rpearcea/polsys.txt,
 
I get the error below. It looks like the error is occurring in the matrix 
row reduction. Does this seem like a bug with the Groebner basis code or 
with the matrix code? 

Thanks so much! 

Best,
Trevor

 ---

ValueErrorTraceback (most recent call last)

 in 

> 1 cProfile.runctx('I.groebner_basis()', globals(), locals(), 
'profile.prof')


/usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/cProfile.py
 
in runctx(statement, globals, locals, filename, sort)

* 17* 

* 18* def runctx(statement, globals, locals, filename=None, sort=-1):

---> 19 return _pyprofile._Utils(Profile).runctx(statement, globals, 
locals,

* 20*  filename, sort)

* 21* 


/usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/profile.py
 
in runctx(self, statement, globals, locals, filename, sort)

* 60* prof = self.profiler()

* 61* try:

---> 62 prof.runctx(statement, globals, locals)

* 63* except SystemExit:

* 64* pass


/usr/local/Cellar/python@3.9/3.9.9/Frameworks/Python.framework/Versions/3.9/lib/python3.9/cProfile.py
 
in runctx(self, cmd, globals, locals)

* 98* self.enable()

* 99* try:

--> 100 exec(cmd, globals, locals)

*101* finally:

*102* self.disable()


 in 


~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/algebras/clifford_algebra.py
 
in groebner_basis(self, term_order)

*   2755* return self._groebner_strategy.groebner_basis

*   2756* self._groebner_strategy = strategy(self)

-> 2757 self._groebner_strategy.compute_groebner()

*   2758* return self._groebner_strategy.groebner_basis

*   2759* 


~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/algebras/exterior_algebra_groebner.pyx
 
in 
sage.algebras.exterior_algebra_groebner.GroebnerStrategy.compute_groebner 
(build/cythonized/sage/algebras/exterior_algebra_groebner.c:8678)()

*221* while P:

*222* Pp = P.pop(min(P))  # The selection: lowest lcm degree

--> 223 Gp = self.reduction(Pp, G)

*224* G.extend(Gp)

*225* for j in range(n, len(G)):


~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/algebras/exterior_algebra_groebner.pyx
 
in sage.algebras.exterior_algebra_groebner.GroebnerStrategy.reduction 
(build/cythonized/sage/algebras/exterior_algebra_groebner.c:7581)()

*178* for m,c in ( 
f)._monomial_coefficients.items()},

*179*sparse=True)

--> 180 M.echelonize()  # Do this in place

*181* lead_supports = 
set(self.leading_supp( f) for f in L)

*182* return [self.E.element_class(self.E, 
{self.int_to_bitset(r - Integer(j)): c for j,c in M[i].iteritems()})


~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/matrix/matrix_rational_sparse.pyx
 
in sage.matrix.matrix_rational_sparse.Matrix_rational_sparse.echelonize 
(build/cythonized/sage/matrix/matrix_rational_sparse.c:7063)()

*524* self.check_mutability()

*525* 

--> 526 pivots = self._echelonize_multimodular(height_guess, proof, 
**kwds)

*527* 

*528* self.cache('in_echelon_form', True)


~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/matrix/matrix_rational_sparse.pyx
 
in 
sage.matrix.matrix_rational_sparse.Matrix_rational_sparse._echelonize_multimodular
 
(build/cythonized/sage/matrix/matrix_rational_sparse.c:7609)()

*571* def _echelonize_multimodular(self, height_guess=None, 
proof=True, **kwds):

*572* cdef Matrix_rational_sparse E

--> 573 E, pivots = self._echelon_form_multimodular(height_guess, 
proof=proof, **kwds)

*574* self.clear_cache()

*575* # Swap the data of E and self (effectively moving E to 
self)


~/Applications/sage/local/var/lib/sage/venv-python3.9/lib/python3.9/site-packages/sage/matrix/matrix_rational_sparse.pyx
 
in 
sage.matrix.matrix_rational_sparse.Matrix_rational_sparse._echelon_form_multimodular
 
(build/cythonized/sage/matrix/matrix_rational_sparse.c:7874)()

*589* from .misc import 
matrix_rational_echelon_form_multimodular

*590* cdef Matrix E

--> 

Re: [sage-devel] Re: Implementing Parent with Facade that is not an Element

[Trevor Karn]

Hi Travis,

Ah got it. Thanks so much!

Best Regards,

Trevor Karn


On Mon, Jun 20, 2022 at 8:11 PM 'Travis Scrimshaw' via sage-devel <
sage-devel@googlegroups.com> wrote:

> Hi Trevor,
>Right...I remember coming across this problem before. Since I know this
> class is for internal use (simply to index a basis), we can override
> __call__() instead of _element_constructor_() as we do not need to invoke
> the coercion framework (and we want this to be fast). This is what the
> subsets code does too.
>
> Best,
> Travis
>
>
> On Tuesday, June 21, 2022 at 1:20:07 AM UTC+9 Trevor Karn wrote:
>
>> Hi all,
>>
>> I am trying to implement a Parent in the category of
>> FiniteEnumeratedSets().Facade(). My hope was to have the finite enumerated
>> sets be represented by `Bitset
>> <https://doc.sagemath.org/html/en/reference/data_structures/sage/data_structures/bitset.html#sage.data_structures.bitset.Bitset>`s.
>> Upon testing, I get the error: TypeError: Cannot convert
>> sage.data_structures.bitset.Bitset to sage.structure.element.Element. I
>> also get the same error when I set facade=True in the Parent.__init__ call.
>> I think this behavior makes sense because (as I understand it) the facade
>> elements should be elements of *some* parent, just not the parent
>> `self`. On the other hand, Bitsets are not an element of any parent.
>>
>> Does anyone have advice on how to proceed? I can think of a few options:
>>
>> - Make Bitsets an Element. This doesn't seem desirable because Bitsets is
>> Cythonized, and as I understand it, Cython doesn't play nice with the
>> Parent/Element framework (please correct me if I misunderstand).
>>
>> - Make an Element class for my Parent which inherits from both element
>> and Bitset. This doesn't seem desirable because I want my parent to be in
>> FiniteEnumeratedSets().Facade().
>>
>> I don't like either of those options, does anyone have suggestions on
>> what else I could do?
>>
>> Thanks so much!
>>
>> -Trevor
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/AJ8HqFgwSGU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/5646a2cb-22d5-43bb-bcbd-b92b0119fb00n%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-devel/5646a2cb-22d5-43bb-bcbd-b92b0119fb00n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAJ6VCMC1mOQLf-rj%2B4J44tH0yBGqkZT00RMq0pmiyA%3DOHC%3DZ0w%40mail.gmail.com.

[sage-devel] Implementing Parent with Facade that is not an Element

[Trevor Karn]

Hi all,

I am trying to implement a Parent in the category of 
FiniteEnumeratedSets().Facade(). My hope was to have the finite enumerated 
sets be represented by `Bitset 
`s.
 
Upon testing, I get the error: TypeError: Cannot convert 
sage.data_structures.bitset.Bitset to sage.structure.element.Element. I 
also get the same error when I set facade=True in the Parent.__init__ call. 
I think this behavior makes sense because (as I understand it) the facade 
elements should be elements of *some* parent, just not the parent `self`. 
On the other hand, Bitsets are not an element of any parent.

Does anyone have advice on how to proceed? I can think of a few options:

- Make Bitsets an Element. This doesn't seem desirable because Bitsets is 
Cythonized, and as I understand it, Cython doesn't play nice with the 
Parent/Element framework (please correct me if I misunderstand).

- Make an Element class for my Parent which inherits from both element and 
Bitset. This doesn't seem desirable because I want my parent to be in 
FiniteEnumeratedSets().Facade().

I don't like either of those options, does anyone have suggestions on what 
else I could do?

Thanks so much!

-Trevor


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/39db7e44-2349-414f-9c0f-4f766c3c10e5n%40googlegroups.com.

Re: [sage-devel] Re: LaTeX printing Hasse diagram

[Trevor Karn]

Thanks so much, Sébastien. I `sage -i dot2tex`-ed on 9.6.beta5 and that 
fixed the problem. Is this something that should be included in the 
documentation? If so, I can open a ticket and add it, but where do you 
suggest I do so? The documentation for `view()` 
<https://doc.sagemath.org/html/en/reference/misc/sage/misc/latex.html#sage.misc.latex.view>
 
seems like too generic of a spot, and as far as I can tell, there is no 
`Poset.view` method in the documentation. One option would be to add a view 
method, but that may conflict with the show method and cause confusion. 

On Friday, April 15, 2022 at 9:54:52 AM UTC-5 Sébastien Labbé wrote:

> Also, now that #20343 is in Sage (9.6.beta7). If graphviz is installed 
> and  `sage -i dot2tex` as well, one can do:
>
> sage: P = Poset((SetPartitions(4), lambda A,B: A in B.refinements()))
> sage: from sage.misc.latex_standalone import TikzPicture
> sage: TikzPicture.from_poset(P, prog='dot').pdf()
>
> The dot graphviz program places the nodes in a tree like form. Valid 
> values for prog are ['dot', 'twopi', 'neato', 'circo', 'fdp'], but they do 
> not create as nice pictures:
>
> sage: TikzPicture.from_poset(P, prog='neato').pdf()
>
> The `from_poset` method is marked as experimental and prints warnings when 
> you use it since it will move in the future within the class Poset. See 
> https://trac.sagemath.org/ticket/33002
>
>
>
>
> On Friday, April 15, 2022 at 3:53:53 PM UTC+2 Trevor Karn wrote:
>
>> Thanks Sébastien, I’ll upgrade and see if that fixes it.
>>
>>
>>
>> On Fri, Apr 15, 2022 at 7:56 AM Sébastien Labbé  wrote:
>>
>>> On 9.6.rc0, I am not able to reproduce the issue. The command 
>>> `view(Poset((SetPartitions(4), lambda A,B: A in B.refinements(` produce 
>>> a nice looking picture level by level.
>>> Sébastien
>>>
>>> On Friday, April 15, 2022 at 3:17:11 AM UTC+2 Trevor Karn wrote:
>>>
>>>> Hi all,
>>>>
>>>> I have tried to create a nice image of a Hasse diagram (of the set 
>>>> partitions of {1,2,3,4}) using the command `view(Poset((SetPartitions(4), 
>>>> lambda A,B: A in B.refinements(`
>>>> as suggested in these notes by Mike Zabrocki 
>>>> <https://garsia.math.yorku.ca/~zabrocki/math4160f19/notes/ch7_mobius_inversion.pdf>
>>>> .
>>>>
>>>> However, when I try, things come out looking a bit messy (image 
>>>> attached). The problem doesn't seem to be with the latex compiler on my 
>>>> end, since (e.g.) the complete bipartite graph comes out looking just fine 
>>>> using `view(graphs.CompleteBipartiteGraph(*3*,*3*))`.
>>>>
>>>> Does this seem like a bug, or are there some configurations wrong on my 
>>>> end?
>>>>
>>>> Thanks,
>>>> Trevor
>>>>
>>>>
>>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "sage-devel" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/sage-devel/rV9qfPdtelU/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> sage-devel+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/b7bf3ffd-383d-45a5-93bf-31ac274c4cc2n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/sage-devel/b7bf3ffd-383d-45a5-93bf-31ac274c4cc2n%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> -- 
>> Best,
>>
>> Trevor
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ce921130-9868-4b95-b79d-b7abde956d4dn%40googlegroups.com.

Re: [sage-devel] Re: LaTeX printing Hasse diagram

[Trevor Karn]

Thanks Sébastien, I’ll upgrade and see if that fixes it.



On Fri, Apr 15, 2022 at 7:56 AM Sébastien Labbé  wrote:

> On 9.6.rc0, I am not able to reproduce the issue. The command
> `view(Poset((SetPartitions(4), lambda A,B: A in B.refinements(` produce
> a nice looking picture level by level.
> Sébastien
>
> On Friday, April 15, 2022 at 3:17:11 AM UTC+2 Trevor Karn wrote:
>
>> Hi all,
>>
>> I have tried to create a nice image of a Hasse diagram (of the set
>> partitions of {1,2,3,4}) using the command `view(Poset((SetPartitions(4),
>> lambda A,B: A in B.refinements(`
>> as suggested in these notes by Mike Zabrocki
>> <https://garsia.math.yorku.ca/~zabrocki/math4160f19/notes/ch7_mobius_inversion.pdf>
>> .
>>
>> However, when I try, things come out looking a bit messy (image
>> attached). The problem doesn't seem to be with the latex compiler on my
>> end, since (e.g.) the complete bipartite graph comes out looking just fine
>> using `view(graphs.CompleteBipartiteGraph(*3*,*3*))`.
>>
>> Does this seem like a bug, or are there some configurations wrong on my
>> end?
>>
>> Thanks,
>> Trevor
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/rV9qfPdtelU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/b7bf3ffd-383d-45a5-93bf-31ac274c4cc2n%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-devel/b7bf3ffd-383d-45a5-93bf-31ac274c4cc2n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
-- 
Best,

Trevor

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAJ6VCMCVpFk1PTO8yiXWnf%3DeZ4vi8tR2T9UvDB02E%3Du6iYsJyw%40mail.gmail.com.

[sage-devel] Re: LaTeX printing Hasse diagram

[Trevor Karn]

Sorry, I should have added: I'm using 9.6.beta5 on MacOS Monterey v. 12.2.

On Thursday, April 14, 2022 at 8:17:11 PM UTC-5 Trevor Karn wrote:

> Hi all,
>
> I have tried to create a nice image of a Hasse diagram (of the set 
> partitions of {1,2,3,4}) using the command `view(Poset((SetPartitions(4), 
> lambda A,B: A in B.refinements(`
> as suggested in these notes by Mike Zabrocki 
> <https://garsia.math.yorku.ca/~zabrocki/math4160f19/notes/ch7_mobius_inversion.pdf>
> .
>
> However, when I try, things come out looking a bit messy (image attached). 
> The problem doesn't seem to be with the latex compiler on my end, since 
> (e.g.) the complete bipartite graph comes out looking just fine using 
> `view(graphs.CompleteBipartiteGraph(*3*,*3*))`.
>
> Does this seem like a bug, or are there some configurations wrong on my 
> end?
>
> Thanks,
> Trevor
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/75b6f7b1-b996-4301-af1d-3f62ef6cc2a2n%40googlegroups.com.

[sage-devel] LaTeX printing Hasse diagram

[Trevor Karn]

Hi all,

I have tried to create a nice image of a Hasse diagram (of the set 
partitions of {1,2,3,4}) using the command `view(Poset((SetPartitions(4), 
lambda A,B: A in B.refinements(`
as suggested in these notes by Mike Zabrocki 

.

However, when I try, things come out looking a bit messy (image attached). 
The problem doesn't seem to be with the latex compiler on my end, since 
(e.g.) the complete bipartite graph comes out looking just fine using 
`view(graphs.CompleteBipartiteGraph(*3*,*3*))`.

Does this seem like a bug, or are there some configurations wrong on my end?

Thanks,
Trevor


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/a4d7d8e7-b570-40cb-9cdc-3cca3b3252e9n%40googlegroups.com.


ugly-hasse.pdf
Description: Adobe PDF document

[sage-devel] Using __slots__ in Sage

[Trevor Karn]

Hi all,

I have just learned about using __slots__ for Python classes. It seems 
interesting to me and I am excited to see that it seems to be faster and 
require less memory. I don't have a specific use case in mind yet, but is 
there anything to be careful about in Sage where using __slots__ might 
break something?

Thanks,
Trevor

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/87b65e16-09ea-4b86-b1c7-4b3744dbf0c9n%40googlegroups.com.

[sage-devel] Re: Bug computing kernel of ring homomorphism GCA

[Trevor Karn]

I forgot to add that Sage does recognize that f(a1*b2) is nonzero:

sage: f(a1*a2)
b1*b2


On Monday, October 18, 2021 at 12:21:47 PM UTC-5 Trevor Karn wrote:

> Hi all,
>
> It looks like I have found a bug in the `.kernel()` method of a ring 
> homomorphism from one  `GradedCommutativeAlgebra` to another. I think I 
> have identified the issue, but was hoping to post here for confirmation 
> that my thinking makes sense before opening a trac ticket and working on a 
> fix. 
>
> *The bug:* let A, B be `GradedCommutativeAlgebra`s each generated by two 
> elements (a_1, a_2 and b_1, b_2 respectively) of degree-1 (so A,B are 
> exterior algebras). Define a homomorphism f: A -> B taking a_1 -> b_1 and 
> a_2 -> b_1 + b_2. 
>
> Then f(a_1a_2) = f(a_1)f(a_2) = b_1(b_1+b_2) = b_1^2 + b_1b_2 = 0 + b_1b2 
> =/= 0.
>
> When I perform the same computation in Sage,  I get:
>
> sage: A = GradedCommutativeAlgebra(QQ,['a1','a2'], (1,1))
> sage: B = GradedCommutativeAlgebra(QQ,['b1','b2'], (1,1))
> sage: A.inject_variables();
> sage: B.inject_variables();
> sage: f = A.hom([b1, b1+b2], codomain=B)
> sage: f.kernel()
> Twosided Ideal (0, a1*a2, 0) of Graded Commutative Algebra with generators 
> ('a1', 'a2') in degrees (1, 1) over Rational Field
>
> which I believe to be incorrect by my computation above. 
>
> *What I think is going wrong:*
> When computing the kernel, the graph ideal is computed as an ideal in the 
> tensor product ring of the domain tensored with the codomain. In 
> constructing this it uses a (commutative) polynomial ring and takes a 
> quotient. In creating the commutative polynomial ring the 
> `.defining_ideal().gens()` method is called on the domain. The 
> `.defining_ideal()` for a noncommutative ring has generators and relations, 
> but calling the `.gens()` method accesses the generators only. For example:
>
> sage: A.defining_ideal()
> Twosided Ideal (a1^2, a2^2) of Noncommutative Multivariate Polynomial Ring 
> in a1, a2 over Rational Field, nc-relations: {a2*a1: -a1*a2}
> sage: A.defining_ideal().gens()
> (a1^2, a2^2)
>
> And so the relation that a2*a1 = - a1*a2 is forgotten in the tensor 
> product ring.
>
> *My proposed fix:*
> Add a function in sage.rings.morphism that computes the tensor product 
> ring when the two rings are noncommutative, then add a check inside of 
> graph_ideal to call _tensor_product_ring_nc as opposed to 
> _tensor_product_ring. 
>
> Does this seem like a reasonable plan, or is there a better approach?
>
> Thanks!
>
> -Trevor
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/21267e96-432a-4cb7-93b9-63e3148dfc72n%40googlegroups.com.

[sage-devel] Bug computing kernel of ring homomorphism GCA

[Trevor Karn]

Hi all,

It looks like I have found a bug in the `.kernel()` method of a ring 
homomorphism from one  `GradedCommutativeAlgebra` to another. I think I 
have identified the issue, but was hoping to post here for confirmation 
that my thinking makes sense before opening a trac ticket and working on a 
fix. 

*The bug:* let A, B be `GradedCommutativeAlgebra`s each generated by two 
elements (a_1, a_2 and b_1, b_2 respectively) of degree-1 (so A,B are 
exterior algebras). Define a homomorphism f: A -> B taking a_1 -> b_1 and 
a_2 -> b_1 + b_2. 

Then f(a_1a_2) = f(a_1)f(a_2) = b_1(b_1+b_2) = b_1^2 + b_1b_2 = 0 + b_1b2 
=/= 0.

When I perform the same computation in Sage,  I get:

sage: A = GradedCommutativeAlgebra(QQ,['a1','a2'], (1,1))
sage: B = GradedCommutativeAlgebra(QQ,['b1','b2'], (1,1))
sage: A.inject_variables();
sage: B.inject_variables();
sage: f = A.hom([b1, b1+b2], codomain=B)
sage: f.kernel()
Twosided Ideal (0, a1*a2, 0) of Graded Commutative Algebra with generators 
('a1', 'a2') in degrees (1, 1) over Rational Field

which I believe to be incorrect by my computation above. 

*What I think is going wrong:*
When computing the kernel, the graph ideal is computed as an ideal in the 
tensor product ring of the domain tensored with the codomain. In 
constructing this it uses a (commutative) polynomial ring and takes a 
quotient. In creating the commutative polynomial ring the 
`.defining_ideal().gens()` method is called on the domain. The 
`.defining_ideal()` for a noncommutative ring has generators and relations, 
but calling the `.gens()` method accesses the generators only. For example:

sage: A.defining_ideal()
Twosided Ideal (a1^2, a2^2) of Noncommutative Multivariate Polynomial Ring 
in a1, a2 over Rational Field, nc-relations: {a2*a1: -a1*a2}
sage: A.defining_ideal().gens()
(a1^2, a2^2)

And so the relation that a2*a1 = - a1*a2 is forgotten in the tensor product 
ring.

*My proposed fix:*
Add a function in sage.rings.morphism that computes the tensor product ring 
when the two rings are noncommutative, then add a check inside of 
graph_ideal to call _tensor_product_ring_nc as opposed to 
_tensor_product_ring. 

Does this seem like a reasonable plan, or is there a better approach?

Thanks!

-Trevor



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/f94883ee-a62f-4904-bb19-d8b59cd37303n%40googlegroups.com.

[sage-devel] Re: Building documentation fails

[Trevor Karn]

This works, thanks so much for your help!

On Saturday, August 14, 2021 at 4:41:57 AM UTC-5 m.c.h...@gmail.com wrote:

> Also during development, I recommend the following command, which only 
> generates the documentation of a single file.
>
> sage --docbuild "file=path/to/my/my_algebra.py" html
>
> Op zaterdag 14 augustus 2021 om 00:20:34 UTC+2 schreef Matthias Koeppe:
>
>> Try "make doc-html". 
>>
>> On Friday, August 13, 2021 at 12:22:44 PM UTC-7 Trevor Karn wrote:
>>
>>> I am trying to build the documentation for a new file I have added to 
>>> sage.algebras, and I am having some trouble. 
>>>
>>> I had used "sage ---docbuild reference html" trying to follow this 
>>> portion of the developers guide. 
>>> <https://doc.sagemath.org/html/en/developer/sage_manuals.html#editing-the-documentation>
>>>  I 
>>> tried "make doc-clean" then "make docbuild" and got the error at the bottom 
>>> of this message.  I'm running 9.4.rc0.
>>>
>>> Does anyone have advice on how to proceed? Thanks in advance!
>>>
>>> -
>>>
>>> trevorkarn@Trevors-MacBook-Air sage % make docbuild 
>>>
>>> /Applications/Xcode.app/Contents/Developer/usr/bin/make 
>>> build/make/Makefile --stop
>>>
>>> make[1]: `build/make/Makefile' is up to date.
>>>
>>> build/bin/sage-logger \
>>>
>>> "cd build/make && ./install 'docbuild'" logs/install.log
>>>
>>> *** ALL ENVIRONMENT VARIABLES BEFORE BUILD: ***
>>>
>>> ACLOCAL_PATH=/usr/local/opt/gettext/share/aclocal:
>>>
>>> CONDA_EXE=/Users/trevorkarn/opt/anaconda3/bin/conda
>>>
>>> CONDA_PYTHON_EXE=/Users/trevorkarn/opt/anaconda3/bin/python
>>>
>>> CONDA_SHLVL=0
>>>
>>>
>>> CPATH=/usr/local/opt/ntl/include:/usr/local/opt/readline/include:/usr/local/include
>>>
>>> DISPLAY=:0
>>>
>>> HOME=/Users/trevorkarn
>>>
>>> LANG=en_US.UTF-8
>>>
>>>
>>> LIBRARY_PATH=/usr/local/opt/ntl/lib:/usr/local/opt/readline/lib:/usr/local/lib
>>>
>>> LOGNAME=trevorkarn
>>>
>>> LaunchInstanceID=2DEE4C06-BA05-4515-8F9D-69431BCDCF45
>>>
>>> MAKE=make
>>>
>>> MAKEFLAGS= V=1
>>>
>>> MAKELEVEL=1
>>>
>>> MFLAGS=
>>>
>>>
>>> PATH=/Users/trevorkarn/Applications/sage/build/bin:/Users/trevorkarn/Applications/sage/src/bin:/Users/trevorkarn/Applications/sage/local/bin:/usr/local/opt/texinfo/bin:/usr/local/opt/gettext/bin:/Users/trevorkarn/opt/anaconda3/condabin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/Library/Apple/usr/bin
>>>
>>>
>>> PKG_CONFIG_PATH=/usr/local/opt/zlib/lib/pkgconfig:/usr/local/opt/sqlite/lib/pkgconfig:/usr/local/opt/readline/lib/pkgconfig:/usr/local/opt/openssl/lib/pkgconfig:/usr/local/opt/openblas/lib/pkgconfig:/usr/local/lib/pkgconfig:
>>>
>>> PWD=/Users/trevorkarn/Applications/sage/build/make
>>>
>>> PYTHONPATH=/Users/trevorkarn/Applications/sage/local
>>>
>>> SAGE_ENV_CONFIG_SOURCED=1
>>>
>>> SAGE_LOCAL=/Users/trevorkarn/Applications/sage/local
>>>
>>> SAGE_LOGFILE=logs/install.log
>>>
>>> SAGE_LOGS=/Users/trevorkarn/Applications/sage/logs/pkgs
>>>
>>> SAGE_NUM_THREADS=1
>>>
>>> SAGE_NUM_THREADS_PARALLEL=4
>>>
>>>
>>> SAGE_ORIG_PATH=/usr/local/opt/texinfo/bin:/usr/local/opt/gettext/bin:/Users/trevorkarn/opt/anaconda3/condabin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/Library/Apple/usr/bin
>>>
>>> SAGE_ORIG_PATH_SET=True
>>>
>>> SAGE_PKGCONFIG=/Users/trevorkarn/Applications/sage/local/lib/pkgconfig
>>>
>>> SAGE_ROOT=/Users/trevorkarn/Applications/sage
>>>
>>> SAGE_SHARE=/Users/trevorkarn/Applications/sage/local/share
>>>
>>> SAGE_SRC=/Users/trevorkarn/Applications/sage/src
>>>
>>> SECURITYSESSIONID=186a8
>>>
>>> SHELL=/bin/zsh
>>>
>>> SHLVL=4
>>>
>>> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.dDZpsjTW4Q/Listeners
>>>
>>> TERM=xterm-256color
>>>
>>> TERM_PROGRAM=Apple_Terminal
>>>
>>> TERM_PROGRAM_VERSION=440
>>>
>>> TERM_SESSION_ID=BFEB78DA-DDB0-4CEC-9077-4FC9DC7BAC3C
>&

[sage-devel] Building documentation fails

[Trevor Karn]

I am trying to build the documentation for a new file I have added to 
sage.algebras, and I am having some trouble. 

I had used "sage ---docbuild reference html" trying to follow this portion 
of the developers guide. 

 I 
tried "make doc-clean" then "make docbuild" and got the error at the bottom 
of this message.  I'm running 9.4.rc0.

Does anyone have advice on how to proceed? Thanks in advance!

-

trevorkarn@Trevors-MacBook-Air sage % make docbuild 

/Applications/Xcode.app/Contents/Developer/usr/bin/make build/make/Makefile 
--stop

make[1]: `build/make/Makefile' is up to date.

build/bin/sage-logger \

"cd build/make && ./install 'docbuild'" logs/install.log

*** ALL ENVIRONMENT VARIABLES BEFORE BUILD: ***

ACLOCAL_PATH=/usr/local/opt/gettext/share/aclocal:

CONDA_EXE=/Users/trevorkarn/opt/anaconda3/bin/conda

CONDA_PYTHON_EXE=/Users/trevorkarn/opt/anaconda3/bin/python

CONDA_SHLVL=0

CPATH=/usr/local/opt/ntl/include:/usr/local/opt/readline/include:/usr/local/include

DISPLAY=:0

HOME=/Users/trevorkarn

LANG=en_US.UTF-8

LIBRARY_PATH=/usr/local/opt/ntl/lib:/usr/local/opt/readline/lib:/usr/local/lib

LOGNAME=trevorkarn

LaunchInstanceID=2DEE4C06-BA05-4515-8F9D-69431BCDCF45

MAKE=make

MAKEFLAGS= V=1

MAKELEVEL=1

MFLAGS=

PATH=/Users/trevorkarn/Applications/sage/build/bin:/Users/trevorkarn/Applications/sage/src/bin:/Users/trevorkarn/Applications/sage/local/bin:/usr/local/opt/texinfo/bin:/usr/local/opt/gettext/bin:/Users/trevorkarn/opt/anaconda3/condabin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/Library/Apple/usr/bin

PKG_CONFIG_PATH=/usr/local/opt/zlib/lib/pkgconfig:/usr/local/opt/sqlite/lib/pkgconfig:/usr/local/opt/readline/lib/pkgconfig:/usr/local/opt/openssl/lib/pkgconfig:/usr/local/opt/openblas/lib/pkgconfig:/usr/local/lib/pkgconfig:

PWD=/Users/trevorkarn/Applications/sage/build/make

PYTHONPATH=/Users/trevorkarn/Applications/sage/local

SAGE_ENV_CONFIG_SOURCED=1

SAGE_LOCAL=/Users/trevorkarn/Applications/sage/local

SAGE_LOGFILE=logs/install.log

SAGE_LOGS=/Users/trevorkarn/Applications/sage/logs/pkgs

SAGE_NUM_THREADS=1

SAGE_NUM_THREADS_PARALLEL=4

SAGE_ORIG_PATH=/usr/local/opt/texinfo/bin:/usr/local/opt/gettext/bin:/Users/trevorkarn/opt/anaconda3/condabin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/Library/Apple/usr/bin

SAGE_ORIG_PATH_SET=True

SAGE_PKGCONFIG=/Users/trevorkarn/Applications/sage/local/lib/pkgconfig

SAGE_ROOT=/Users/trevorkarn/Applications/sage

SAGE_SHARE=/Users/trevorkarn/Applications/sage/local/share

SAGE_SRC=/Users/trevorkarn/Applications/sage/src

SECURITYSESSIONID=186a8

SHELL=/bin/zsh

SHLVL=4

SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.dDZpsjTW4Q/Listeners

TERM=xterm-256color

TERM_PROGRAM=Apple_Terminal

TERM_PROGRAM_VERSION=440

TERM_SESSION_ID=BFEB78DA-DDB0-4CEC-9077-4FC9DC7BAC3C

TMPDIR=/var/folders/n4/krml6vf978lgy2n0n63_k584gn/T/

USER=trevorkarn

XPC_FLAGS=0x0

XPC_SERVICE_NAME=0

_=/usr/bin/env

_CE_CONDA=

_CE_M=

__CFBundleIdentifier=com.apple.Terminal

__CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0

***

make[1]: *** No rule to make target `docbuild'.  Stop.


real 0m0.113s

user 0m0.067s

sys 0m0.014s

***

Error building Sage.


The following package(s) may have failed to build (not necessarily

during this run of 'make docbuild'):


It is safe to delete any log files and build directories, but they

contain information that is helpful for debugging build problems.

WARNING: If you now run 'make' again, the build directory of the

same version of the package will, by default, be deleted. Set the

environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.


make: *** [docbuild] Error 1

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/33c9226d-333a-4827-8ac7-84a1406da206n%40googlegroups.com.

[sage-devel] Re: How to use generic quotients?

[Trevor Karn]

I'm glad it was helpful! I think I'd like to add a NotImplementedError on 
the Ideal_nc.reduce() method until we are able to implement the quotients 
in #32249. Does anyone see any reason not to implement such an error? Or at 
least a warning?

On Tuesday, July 27, 2021 at 8:33:13 AM UTC-5 Michael Jung wrote:

> Thank you Trevor! This was extremely helpful!
> Trevor Karn schrieb am Dienstag, 27. Juli 2021 um 14:23:37 UTC+2:
>
>> Check out this ask.sagemath.org post: 
>> https://ask.sagemath.org/question/56243/quotients-of-exterior-algebras/. 
>> You could try to implement a specific ideal for the graded commutative 
>> algebras. I opened a ticket https://trac.sagemath.org/ticket/32249 to 
>> start doing this but in the meantime got pulled toward other tasks for my 
>> GSoC project. 
>>
>> On Monday, July 26, 2021 at 1:43:33 PM UTC-5 Michael Jung wrote:
>>
>>> Sorry, the last example is of course
>>>
>>> sage: from sage.algebras.commutative_graded_algebra_finite import 
>>> FiniteGCAlgebra
>>> sage: A. = FiniteGCAlgebra(QQ, degrees=(1,2,3), max_degree=6)
>>> sage: I = A.ideal(y^2)
>>> sage: Q = A.quotient(I)
>>> sage: Q.gen(1)^2
>>> ybar^2
>>>
>>> Michael Jung schrieb am Montag, 26. Juli 2021 um 20:40:25 UTC+2:
>>>
>>>> Hello everyone,
>>>>
>>>> In https://trac.sagemath.org/ticket/32272, I am trying to implement 
>>>> graded algebras with finite degree. I have troubles constructing a 
>>>> (generic) quotient. Here is what happens without a ngens method:
>>>>
>>>> sage: from sage.algebras.commutative_graded_algebra_finite import 
>>>> FiniteGCAlgebra
>>>> sage: A. = FiniteGCAlgebra(QQ, degrees=(1,2,3), max_degree=6)
>>>> sage: I = A.ideal(y^2)
>>>> sage: A.quotient(I)
>>>> Traceback (most recent call last)
>>>> ...
>>>> RuntimeError: Graded commutative algebra with generators ('x', 'y', 
>>>> 'z') in degrees (1, 2, 3) with maximal finite degree 6 still using old 
>>>> coercion framework
>>>>
>>>> Adding a ngens method on the other hand causes the quotients not to 
>>>> function properly:
>>>>
>>>> sage: from sage.algebras.commutative_graded_algebra_finite import 
>>>> FiniteGCAlgebra
>>>> sage: A. = FiniteGCAlgebra(QQ, degrees=(1,2,3), max_degree=6)
>>>> sage: I = A.ideal(y^2)
>>>> sage: Q = A.quotient(I)
>>>> sage: Q.gen(0)*Q.gen(1)
>>>> xbar*ybar
>>>>
>>>> The result, however, should be zero.
>>>>
>>>> What am I doing wrong? Help is very 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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/ccbdd5e3-cae3-4d71-80bf-976fb5c2fe1bn%40googlegroups.com.

[sage-devel] Re: How to use generic quotients?

[Trevor Karn]

Check out this ask.sagemath.org 
post: https://ask.sagemath.org/question/56243/quotients-of-exterior-algebras/. 
You could try to implement a specific ideal for the graded commutative 
algebras. I opened a ticket https://trac.sagemath.org/ticket/32249 to start 
doing this but in the meantime got pulled toward other tasks for my GSoC 
project. 

On Monday, July 26, 2021 at 1:43:33 PM UTC-5 Michael Jung wrote:

> Sorry, the last example is of course
>
> sage: from sage.algebras.commutative_graded_algebra_finite import 
> FiniteGCAlgebra
> sage: A. = FiniteGCAlgebra(QQ, degrees=(1,2,3), max_degree=6)
> sage: I = A.ideal(y^2)
> sage: Q = A.quotient(I)
> sage: Q.gen(1)^2
> ybar^2
>
> Michael Jung schrieb am Montag, 26. Juli 2021 um 20:40:25 UTC+2:
>
>> Hello everyone,
>>
>> In https://trac.sagemath.org/ticket/32272, I am trying to implement 
>> graded algebras with finite degree. I have troubles constructing a 
>> (generic) quotient. Here is what happens without a ngens method:
>>
>> sage: from sage.algebras.commutative_graded_algebra_finite import 
>> FiniteGCAlgebra
>> sage: A. = FiniteGCAlgebra(QQ, degrees=(1,2,3), max_degree=6)
>> sage: I = A.ideal(y^2)
>> sage: A.quotient(I)
>> Traceback (most recent call last)
>> ...
>> RuntimeError: Graded commutative algebra with generators ('x', 'y', 'z') 
>> in degrees (1, 2, 3) with maximal finite degree 6 still using old coercion 
>> framework
>>
>> Adding a ngens method on the other hand causes the quotients not to 
>> function properly:
>>
>> sage: from sage.algebras.commutative_graded_algebra_finite import 
>> FiniteGCAlgebra
>> sage: A. = FiniteGCAlgebra(QQ, degrees=(1,2,3), max_degree=6)
>> sage: I = A.ideal(y^2)
>> sage: Q = A.quotient(I)
>> sage: Q.gen(0)*Q.gen(1)
>> xbar*ybar
>>
>> The result, however, should be zero.
>>
>> What am I doing wrong? Help is very 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.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c98f82f0-e0e6-4d34-a1e1-466f4c10e792n%40googlegroups.com.

Re: [sage-devel] Re: Rebuilding while developing?

[Trevor Karn]

Awesome thank you!

On Tue, Jul 6, 2021 at 8:35 PM Kwankyu Lee  wrote:

>
>
> On Wednesday, July 7, 2021 at 4:55:15 AM UTC+9 Trevor Karn wrote:
>
>> Hi there,
>>
>> I'm currently working on upgrading to sage 9.4.beta4 from source. I'm not
>> having any trouble with it (so far), but I was hoping to keep writing some
>> code. I'm concerned that if I edit code while sage is ```make build``-ing
>> that I will break things. Is it the case that editing the source while
>> building a new beta version will break things? Or is it safe to do so?
>>
>
> It is not safe to say it is safe. But it usually does not break things if
> you edit python files while building.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/jDitnf13ZWc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/6f21af40-5b06-4e16-a180-c366fc670ea5n%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-devel/6f21af40-5b06-4e16-a180-c366fc670ea5n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
-- 
Best,

Trevor

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAJ6VCMCYPJw1QeFbk6ohuR%3D10jkevQ6DE-ksPAyD%2Br7XOksShw%40mail.gmail.com.

[sage-devel] Rebuilding while developing?

[Trevor Karn]

Hi there,

I'm currently working on upgrading to sage 9.4.beta4 from source. I'm not 
having any trouble with it (so far), but I was hoping to keep writing some 
code. I'm concerned that if I edit code while sage is ```make build``-ing 
that I will break things. Is it the case that editing the source while 
building a new beta version will break things? Or is it safe to do so?

Thanks so much!

-Trevor

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/919b3472-03a4-41f2-99d8-2c12fd59524dn%40googlegroups.com.

[sage-devel] Re: GSoC 2021 - Introduction - BTerms project

[Trevor Karn]

Hi Thomas and David,

Nice to meet you. I'm also participating in GSoC this summer. Looking 
forward to seeing everything that comes out of this summer!

Best,
Trevor

On Tuesday, June 8, 2021 at 10:19:07 AM UTC-5 davida...@gmail.com wrote:

> Hello Thomas!
>
> I'm also participating in GSoC this summer. If you need help with any 
> mathematical stuff you can ask me, I'll be glad to help you. 
>
> I'm looking forward to learn more about your project.
>
> Best,
>
> David A.
>
> Le lundi 7 juin 2021 à 09:11:28 UTC-4, Thomas Hagelmayer a écrit :
>
>> Hello everybody,
>>
>> My name is Thomas Hagelmayer and I am currently in the last semester 
>> before obtaining my Bachelor’s degree in Applied Computer Science at the 
>> Univeristy of Klagenfurt. I'm currently participating in the program Google 
>> Summer of Code 2021 for SageMath where I will be adding support for error 
>> terms with explicit constants to AsymptoticRing (mentored by Clemens 
>> Heuberger and Benjamin Hackl). We will call them BTerms. This will be my 
>> first contribution to SageMath and I am very excited to be working on this 
>> project.
>>
>> This is the meta trac ticket which will contain other tickets related to 
>> the project:
>>
>> #31922 
>>
>> Any comments and/or suggestions are more than welcome.
>>
>> Kind regards
>> Thomas Hagelmayer 
>>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/1124bcfc-ae09-42a4-8765-ca611e6a00e7n%40googlegroups.com.

[sage-combinat-devel] GSoC Orlik-Solomon and Orlik-Terao

[Trevor Karn]

Hi all,

I'm Trevor, a grad student at the University of Minnesota - Twin Cities. 
I'll be working on Sage this summer through the Google Summer of Code. My 
goal is to implement invariant algebras and in particular, develop some 
more tools for Orlik-Solomon and Orlik-Terao algebras. More details are 
here.  

If anyone has anything they'd like to see in this implementation, I'd be 
happy to hear it so I can try to include it.

Thanks,
Trevor

-- 
You received this message because you are subscribed to the Google Groups 
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-combinat-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-combinat-devel/17696bd5-73d9-449a-80e9-b41591672995n%40googlegroups.com.

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I would be willing to help make improvements to the manual, my only
hesitation is that I'm not 100% sure what is going on with the
bootstrapping. Is there anything particular to bootstrapping in Sage that
wouldn't show up in googling around about it?

Best Regards,

Trevor Karn


On Tue, Feb 9, 2021 at 1:15 PM Matthias Koeppe 
wrote:

> On Tuesday, February 9, 2021 at 9:09:32 AM UTC-8 zsc...@gmail.com wrote:
>
>> I see that the link I posted to the installation from source
>> documentation doesn't mention autoconf/automake, but I would have thought
>> some other package would have already installed them.  Probably since
>> homebrew is all bottles now they don't automatically get installed anymore
>> if you are not building locally.
>>
>> But Dima is right, it's probably best practice to brew install the
>> packages listed in the file build/pkgs/_bootstrap/distros/homebrew.txt.
>>
>>>
>>>
> The installation manual does not mention the bootstrapping prerequisites
> because users installing source releases will not need them.
> Bootstrapping is only needed when developers use branches from git that
> make changes to packages or build scripts.
>
> However the developer's manual should be updated to discuss bootstrapping.
>
> There is a ticket for improvements to this manual -
> https://trac.sagemath.org/ticket/29784 - which needs help.
>
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/TmbLnmwz2mg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/43f209e5-8536-4685-8c9d-78e5eeb0aa84n%40googlegroups.com
> <https://groups.google.com/d/msgid/sage-devel/43f209e5-8536-4685-8c9d-78e5eeb0aa84n%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAJ6VCMDGmFZ%2BOqofD2t8_-yjd3FapZtY%3DPF_Nhz%3DFJoGLyKuuA%40mail.gmail.com.

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I uninstalled and reinstalled homebrew and that got rid of the brew doctor
warnings. I then brewed the suggested packages from the Sage link Zachary
provided and the packages listed at the end of the output of configure.

Then from SAGE_ROOT I ran

make distclean
source .homebrew-build-env
./bootstrap -d
./configure
make -j4 build

In the end this seems to be working. Thank you so much Dima and Zachary for
your help.

The reason for running ./bootstrap with the -d flag was because that is
what an error message told me to do. Without -d flag:

trevorkarn@Trevors-MacBook-Air sage % source .homebrew-build-env

trevorkarn@Trevors-MacBook-Air sage % ./bootstrap

rm -rf config configure build/make/Makefile-auto.in

rm -f src/doc/en/installation/*.txt

rm -rf src/doc/en/reference/spkg/*.rst

rm -f src/doc/en/reference/repl/*.txt

rm -f environment.yml

rm -f src/environment.yml

rm -f environment-optional.yml

rm -f src/environment-optional.yml

src/doc/bootstrap:92: installing src/doc/en/installation/arch.txt and
src/doc/en/installation/arch-optional.txt

src/doc/bootstrap:92: installing src/doc/en/installation/debian.txt and
src/doc/en/installation/debian-optional.txt

src/doc/bootstrap:92: installing src/doc/en/installation/fedora.txt and
src/doc/en/installation/fedora-optional.txt

src/doc/bootstrap:92: installing src/doc/en/installation/cygwin.txt and
src/doc/en/installation/cygwin-optional.txt

src/doc/bootstrap:92: installing src/doc/en/installation/homebrew.txt and
src/doc/en/installation/homebrew-optional.txt

src/doc/bootstrap:66: installing environment.yml, environment-optional.yml,
src/environment.yml and src/environment-optional.yml

src/doc/bootstrap:103: installing src/doc/en/reference/spkg/*.rst

src/doc/bootstrap:182: installing src/doc/en/reference/repl/options.txt

bootstrap:73: installing 'config/config.rpath'

./bootstrap: line 118: aclocal: command not found

Bootstrap failed. Either install autotools or run bootstrap with

the -d option to download the auto-generated files instead.

Best Regards,

Trevor Karn


On Tue, Feb 9, 2021 at 4:06 AM Dima Pasechnik  wrote:

> On Tue, Feb 9, 2021 at 4:07 AM Zachary Scherr  wrote:
> >
> > I need to sign off for the night, but the numpy error is definitely
> related to gfortran.  If you have gcc installed via homebrew then it should
> come with the latest version of gfortran.  You can see from your config.log
> file that gfortran is not found:
> >
> > configure:7281: checking for gfortran
> > configure:7311: result: no
> >
> > and other standard homebrew packages are not found, like openblas:
> >
> > configure:12171: checking BLAS library
> > configure:12190: result: openblas
> > configure:12239: checking whether any of gfortran is installed as or
> will be installed as SPKG
> > configure:12243: result: yes; install openblas as well
> > configure:13540: no suitable system package found for SPKG openblas
> >
> > are you aware if you have gcc and openblas installed via homebrew? I
> also see that you didn't run "source .homebrew-build-env" before running
> ./configure since I don't see certain items on your path.  If you go to the
> sage installation guide at
> https://doc.sagemath.org/html/en/installation/source.html#macos-recommended-installation
> you can see a list of homebrew packages you might want to have before
> installing sage.  I think if you get everything in working order with
> homebrew then you shouldn't have any issues installing sage.  Here is my
> best suggestion as to what to try:
> >
> > - fix all "brew doctor" warnings.  This might not be necessary, but I
> get worried when I see so many warnings.  You can probably just delete all
> the suggested files and you should be fine.
> >
> > - install all the recommended homebrew packages.  If any are already
> installed then maybe try "brew reinstall" to make sure it is installed
> properly.  If you think you have homebrew gcc installed then you should be
> able to do "which gfortran" and "gfortran --version".  That should
> hopefully show you that you have gfortran 10.2.0_3.
> >
> > - in your sage folder under the develop branch you should run the
> commands I mentioned, and don't skip out on "source .homebrew-build-env":
> >
> > >> make distclean
> > >> ./bootstrap
> > >> source .homebrew-build-env
> > >> ./configure
> >
> > Before running "make -j4 build" you can look at config.log and make sure
> that it picked up all of the relevant homebrew packages.
> >
> >
> source .homebrew-build-env
>
> should be run before ./bootstrap
>
>
> as well, ./confugure at the end of its run outputs an advice on
> packages that can still be install

Re: [sage-devel] Trouble building cython

[Trevor Karn]

brew doctor is giving lots of errors about unbrewed files:

trevorkarn@Trevors-MacBook-Air sage % brew doctor

*Please note that these warnings are just used to help the Homebrew
maintainers*

*with debugging if you file an issue. If everything you use Homebrew for is*

*working fine: please don't worry or file an issue; just ignore this.
Thanks!*


Warning: Unbrewed dylibs were found in /usr/local/lib.

If you didn't put them there on purpose they could cause problems when

building Homebrew formulae, and may need to be deleted.


Unexpected dylibs:

  /usr/local/lib/libtcl8.6.dylib

  /usr/local/lib/libtk8.6.dylib


Warning: Unbrewed header files were found in /usr/local/include.

If you didn't put them there on purpose they could cause problems when

building Homebrew formulae, and may need to be deleted.


Unexpected header files:

  /usr/local/include/fakemysql.h

  /usr/local/include/fakepq.h

  /usr/local/include/fakesql.h

  /usr/local/include/itcl.h

  /usr/local/include/itcl2TclOO.h

  /usr/local/include/itclDecls.h

  /usr/local/include/itclInt.h

  /usr/local/include/itclIntDecls.h

  /usr/local/include/itclMigrate2TclCore.h

  /usr/local/include/itclTclIntStubsFcn.h

  /usr/local/include/mysqlStubs.h

  /usr/local/include/odbcStubs.h

  /usr/local/include/pqStubs.h

  /usr/local/include/tcl.h

  /usr/local/include/tclDecls.h

  /usr/local/include/tclOO.h

  /usr/local/include/tclOODecls.h

  /usr/local/include/tclPlatDecls.h

  /usr/local/include/tclThread.h

  /usr/local/include/tclTomMath.h

  /usr/local/include/tclTomMathDecls.h

  /usr/local/include/tdbc.h

  /usr/local/include/tdbcDecls.h

  /usr/local/include/tdbcInt.h

  /usr/local/include/tk.h

  /usr/local/include/tkDecls.h

  /usr/local/include/tkPlatDecls.h


Warning: Unbrewed '.pc' files were found in /usr/local/lib/pkgconfig.

If you didn't put them there on purpose they could cause problems when

building Homebrew formulae, and may need to be deleted.


Unexpected '.pc' files:

  /usr/local/lib/pkgconfig/tcl.pc

  /usr/local/lib/pkgconfig/tk.pc


Warning: Unbrewed static libraries were found in /usr/local/lib.

If you didn't put them there on purpose they could cause problems when

building Homebrew formulae, and may need to be deleted.


Unexpected static libraries:

  /usr/local/lib/libtclstub8.6.a

  /usr/local/lib/libtkstub8.6.a


Warning: You have unlinked kegs in your Cellar.

Leaving kegs unlinked can lead to build-trouble and cause formulae that
depend on

those kegs to fail to run properly once built. Run `brew link` on these:

  ffmpeg

  ghostscript


Warning: Homebrew's "sbin" was not found in your PATH but you have installed

formulae that put executables in /usr/local/sbin.

Consider setting your PATH for example like so:

  echo 'export PATH="/usr/local/sbin:$PATH"' >> ~/.zshrc


Warning: Broken symlinks were found. Remove them with `brew cleanup`:

  /usr/local/bin/git-trac

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy10.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy5.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy6.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy7.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy8.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasy9.pfb

  /usr/local/share/ghostscript/9.27/Resource/Font/wasyb10.pfb

  /usr/local/share/man/man1/brew-cask.1

  /usr/local/share/zsh/site-functions/_brew_cask

trevorkarn@Trevors-MacBook-Air sage % brew cleanup

Removing: /usr/local/Cellar/gettext/0.20.1... (1,899 files, 18.5MB)

Removing: /usr/local/Cellar/gmp/6.1.2_2... (18 files, 3.1MB)

Removing: /usr/local/Cellar/gnutls/3.6.9... (1,227 files, 9.9MB)

Removing: /usr/local/Cellar/icu4c/64.2... (257 files, 69.2MB)

Removing: /usr/local/Cellar/libevent/2.1.11... (1,063 files, 5MB)

Removing: /usr/local/Cellar/libffi/3.2.1... (16 files, 296.8KB)

Removing: /usr/local/Cellar/libidn2/2.2.0_1... (70 files, 700.9KB)

Removing: /usr/local/Cellar/libtasn1/4.14... (59 files, 384KB)

Removing: /usr/local/Cellar/nettle/3.4.1... (85 files, 2MB)

Error: Interrupted system call @ dir_initialize - /usr/local/Cellar/opus

trevorkarn@Trevors-MacBook-Air sage % ;2D

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 8:38 PM Zachary Scherr  wrote:

> In your original config.log, it looked like sage was picking up its own
> fortran:
>
> configure:11991: gfortran has already been installed by SageMath
> configure:39396: result: gfortran-9.2.0:
>  already installed as an SPKG
>
> The current version of gfortran from homebrew is 10.2.0 version 3
>
> GNU Fortran (Homebrew GCC 10.2.0_3) 10.2.0
> Copyright (C) 2020 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> ./configure should be picking up homebrew's gfortran (installed with gcc),
> and it see

Re: [sage-devel] Trouble building cython

[Trevor Karn]

Unfortunately, that did not seem to work.

Here are the last few lines of the terminal output and I've attached the
numpy log.

[singular-4.1.1p2.p0] real 28m38.843s

[singular-4.1.1p2.p0] user 24m18.545s

[singular-4.1.1p2.p0] sys 3m53.423s

[singular-4.1.1p2.p0] Copying package files from temporary location
/Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/singular-4.1.1p2.p0/inst
to /Users/trevorkarn/Applications/sage/local

[singular-4.1.1p2.p0] Successfully installed singular-4.1.1p2.p0

[singular-4.1.1p2.p0] Deleting temporary build directory

[singular-4.1.1p2.p0]
/Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/singular-4.1.1p2.p0

[singular-4.1.1p2.p0] Finished installing singular-4.1.1p2.p0

make[2]: *** [all-build] Error 2


real 182m14.796s

user 355m33.883s

sys 72m32.388s

***

Error building Sage.


The following package(s) may have failed to build (not necessarily

during this run of 'make all-build'):


* package: numpy-1.19.4

  last build time: Feb 8 19:48

  log file:
/Users/trevorkarn/Applications/sage/logs/pkgs/numpy-1.19.4.log

  build directory:
/Users/trevorkarn/Applications/sage/local/var/tmp/sage/build/numpy-1.19.4


It is safe to delete any log files and build directories, but they

contain information that is helpful for debugging build problems.

WARNING: If you now run 'make' again, the build directory of the

same version of the package will, by default, be deleted. Set the

environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.


make[1]: *** [all-build] Error 1

make: *** [build] Error 2

trevorkarn@Trevors-MacBook-Air sage %


Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 1:56 PM Zachary Scherr  wrote:

> yea, something seems messed up.  For example, the numpy problem was fixed
> on beta 6 and should still be fixed in beta 7.  It looks like somehow you
> have old files hanging around which are causing problems.  Hopefully make
> distclean will clean everything and let you start fresh.
>
> On Monday, February 8, 2021 at 2:25:16 PM UTC-5 Trevor Karn wrote:
>
>> I must have typed it wrong. The second option you gave failed on numpy,
>> but I tried the first option again, and it is compiling.
>>
>> Best Regards,
>>
>> Trevor Karn
>>
>>
>> On Mon, Feb 8, 2021 at 11:31 AM Zachary Scherr  wrote:
>>
>>> Are you sure you typed it correctly? Maybe try running
>>>
>>> ./bootstrap
>>>
>>> to make sure that the make targets are in order.
>>>
>>> On Monday, February 8, 2021 at 12:27:01 PM UTC-5 Trevor Karn wrote:
>>>
>>>> I tried make distclean and got an error “make: *** No rule to make
>>>> target ‘distclean’. Stop.”
>>>>
>>>> So I tried your second suggestion and it seems to be working so far,
>>>> but it is still compiling.
>>>>
>>>> On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr 
>>>> wrote:
>>>>
>>>>> Probably the thing to try would be:
>>>>>
>>>>> make distclean
>>>>>
>>>>> and then you can build from scratch via:
>>>>>
>>>>> ./bootstrap
>>>>> source .homebrew-build-env
>>>>> ./configure
>>>>> make -j4 build
>>>>>
>>>>> But if you want to try cleaning wheel first before starting from
>>>>> scratch, you could just try
>>>>>
>>>>> make wheel-clean
>>>>> make -j4 build
>>>>>
>>>>> but it might be better to clean everything and start from scratch.
>>>>>
>>>>> On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:
>>>>>
>>>>>> I do not see pep425tags.py in that directory.
>>>>>>
>>>>>> trevorkarn@Trevors-MacBook-Air sage % cd
>>>>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>>>>>>
>>>>>> trevorkarn@Trevors-MacBook-Air wheel % ls
>>>>>>
>>>>>> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>>>>>>
>>>>>> __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored
>>>>>>
>>>>>> Is there a way to clean the build environment?
>>>>>>
>>>>>> Best Regards,
>>>>>>
>>>>>> Trevor Karn
>>>>>>
>>>>>>
>>>>>> On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik 
>>>>>> wrote:
>>>>>>
>>>

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I must have typed it wrong. The second option you gave failed on numpy, but
I tried the first option again, and it is compiling.

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 11:31 AM Zachary Scherr  wrote:

> Are you sure you typed it correctly? Maybe try running
>
> ./bootstrap
>
> to make sure that the make targets are in order.
>
> On Monday, February 8, 2021 at 12:27:01 PM UTC-5 Trevor Karn wrote:
>
>> I tried make distclean and got an error “make: *** No rule to make target
>> ‘distclean’. Stop.”
>>
>> So I tried your second suggestion and it seems to be working so far, but
>> it is still compiling.
>>
>> On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr  wrote:
>>
>>> Probably the thing to try would be:
>>>
>>> make distclean
>>>
>>> and then you can build from scratch via:
>>>
>>> ./bootstrap
>>> source .homebrew-build-env
>>> ./configure
>>> make -j4 build
>>>
>>> But if you want to try cleaning wheel first before starting from
>>> scratch, you could just try
>>>
>>> make wheel-clean
>>> make -j4 build
>>>
>>> but it might be better to clean everything and start from scratch.
>>>
>>> On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:
>>>
>>>> I do not see pep425tags.py in that directory.
>>>>
>>>> trevorkarn@Trevors-MacBook-Air sage % cd
>>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>>>>
>>>> trevorkarn@Trevors-MacBook-Air wheel % ls
>>>>
>>>> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>>>>
>>>> __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored
>>>>
>>>> Is there a way to clean the build environment?
>>>>
>>>> Best Regards,
>>>>
>>>> Trevor Karn
>>>>
>>>>
>>>> On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  wrote:
>>>>
>>>>> the only explanation for pep425tags.py would be an unclean build
>>>>> environment - e.g. weird env vars set, or strange stuff in PATH.
>>>>>
>>>>> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr 
>>>>> wrote:
>>>>> >
>>>>> > and do you see that pep425tags.py file in that directory?
>>>>> >
>>>>> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
>>>>> >>
>>>>> >> The only contents of the file you pointed me towards are
>>>>> >>
>>>>> >> __version__ = '0.36.2'
>>>>> >>
>>>>> >> Best Regards,
>>>>> >>
>>>>> >> Trevor Karn
>>>>> >>
>>>>> >>
>>>>> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr 
>>>>> wrote:
>>>>> >>>
>>>>> >>> I really don't understand.  The Cython log file shows that the
>>>>> problem is in
>>>>> >>>
>>>>> >>>
>>>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>>>>> >>>
>>>>> >>> I could be mistaken, but I don't think pep425tags.py has been a
>>>>> part of the wheel package for a while now.  Certainly when I looked at
>>>>> wheel on my sage there was no such file.
>>>>> >>>
>>>>> >>> Can you go to your
>>>>> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
>>>>> directory and take a look at __init__.py.  Does the version say 0.36.2?
>>>>> >>>
>>>>> >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> Here is what I get. It seems like it is the same as yours?
>>>>> >>>>
>>>>> >>>>
>>>>> >>>> trevorkarn@Trevors-MacBook-Air sage % brew info python3
>>>>> >>>>
>>>>> >>>> python@3.9: stable 3.9.1
>>>>> >>>>
>>>>> >>>> Interpreted, interactive, object-oriented programming language
>>>>> >>>>
>>>>> >>>> https

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I tried make distclean and got an error “make: *** No rule to make target
‘distclean’. Stop.”

So I tried your second suggestion and it seems to be working so far, but it
is still compiling.

On Mon, Feb 8, 2021 at 10:29 AM Zachary Scherr  wrote:

> Probably the thing to try would be:
>
> make distclean
>
> and then you can build from scratch via:
>
> ./bootstrap
> source .homebrew-build-env
> ./configure
> make -j4 build
>
> But if you want to try cleaning wheel first before starting from scratch,
> you could just try
>
> make wheel-clean
> make -j4 build
>
> but it might be better to clean everything and start from scratch.
>
> On Monday, February 8, 2021 at 10:59:05 AM UTC-5 Trevor Karn wrote:
>
>> I do not see pep425tags.py in that directory.
>>
>> trevorkarn@Trevors-MacBook-Air sage % cd
>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/
>>
>> trevorkarn@Trevors-MacBook-Air wheel % ls
>>
>> __init__.py __pycache__ cli metadata.py util.py wheelfile.py
>>
>> __main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored
>>
>> Is there a way to clean the build environment?
>>
>> Best Regards,
>>
>> Trevor Karn
>>
>>
>> On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  wrote:
>>
>>> the only explanation for pep425tags.py would be an unclean build
>>> environment - e.g. weird env vars set, or strange stuff in PATH.
>>>
>>> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr  wrote:
>>> >
>>> > and do you see that pep425tags.py file in that directory?
>>> >
>>> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
>>> >>
>>> >> The only contents of the file you pointed me towards are
>>> >>
>>> >> __version__ = '0.36.2'
>>> >>
>>> >> Best Regards,
>>> >>
>>> >> Trevor Karn
>>> >>
>>> >>
>>> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr 
>>> wrote:
>>> >>>
>>> >>> I really don't understand.  The Cython log file shows that the
>>> problem is in
>>> >>>
>>> >>>
>>> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>>> >>>
>>> >>> I could be mistaken, but I don't think pep425tags.py has been a part
>>> of the wheel package for a while now.  Certainly when I looked at wheel on
>>> my sage there was no such file.
>>> >>>
>>> >>> Can you go to your
>>> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
>>> directory and take a look at __init__.py.  Does the version say 0.36.2?
>>> >>>
>>> >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
>>> >>>>
>>> >>>>
>>> >>>> Here is what I get. It seems like it is the same as yours?
>>> >>>>
>>> >>>>
>>> >>>> trevorkarn@Trevors-MacBook-Air sage % brew info python3
>>> >>>>
>>> >>>> python@3.9: stable 3.9.1
>>> >>>>
>>> >>>> Interpreted, interactive, object-oriented programming language
>>> >>>>
>>> >>>> https://www.python.org/
>>> >>>>
>>> >>>> /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>>> >>>>
>>> >>>>   Built from source on 2021-02-05 at 16:39:31
>>> >>>>
>>> >>>> From:
>>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>>> >>>>
>>> >>>> License: Python-2.0
>>> >>>>
>>> >>>> ==> Dependencies
>>> >>>>
>>> >>>> Build: pkg-config ✔
>>> >>>>
>>> >>>> Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔,
>>> xz ✔
>>> >>>>
>>> >>>> ==> Caveats
>>> >>>>
>>> >>>> Python has been installed as
>>> >>>>
>>> >>>>   /usr/local/bin/python3
>>> >>>>
>>> >>>>
>>> >>>> Unversioned symlinks `python`, `python-config`, `pip` etc. pointing
>>> to
>>> >>>>
>&g

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I do not see pep425tags.py in that directory.

trevorkarn@Trevors-MacBook-Air sage % cd
/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/

trevorkarn@Trevors-MacBook-Air wheel % ls

__init__.py __pycache__ cli metadata.py util.py wheelfile.py

__main__.py bdist_wheel.py macosx_libfile.py pkginfo.py vendored

Is there a way to clean the build environment?

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 9:54 AM Dima Pasechnik  wrote:

> the only explanation for pep425tags.py would be an unclean build
> environment - e.g. weird env vars set, or strange stuff in PATH.
>
> On Mon, Feb 8, 2021 at 3:51 PM Zachary Scherr  wrote:
> >
> > and do you see that pep425tags.py file in that directory?
> >
> > On Monday, February 8, 2021 at 10:21:09 AM UTC-5 Trevor Karn wrote:
> >>
> >> The only contents of the file you pointed me towards are
> >>
> >> __version__ = '0.36.2'
> >>
> >> Best Regards,
> >>
> >> Trevor Karn
> >>
> >>
> >> On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  wrote:
> >>>
> >>> I really don't understand.  The Cython log file shows that the problem
> is in
> >>>
> >>>
> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
> >>>
> >>> I could be mistaken, but I don't think pep425tags.py has been a part
> of the wheel package for a while now.  Certainly when I looked at wheel on
> my sage there was no such file.
> >>>
> >>> Can you go to your
> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
> directory and take a look at __init__.py.  Does the version say 0.36.2?
> >>>
> >>> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
> >>>>
> >>>>
> >>>> Here is what I get. It seems like it is the same as yours?
> >>>>
> >>>>
> >>>> trevorkarn@Trevors-MacBook-Air sage % brew info python3
> >>>>
> >>>> python@3.9: stable 3.9.1
> >>>>
> >>>> Interpreted, interactive, object-oriented programming language
> >>>>
> >>>> https://www.python.org/
> >>>>
> >>>> /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
> >>>>
> >>>>   Built from source on 2021-02-05 at 16:39:31
> >>>>
> >>>> From:
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
> >>>>
> >>>> License: Python-2.0
> >>>>
> >>>> ==> Dependencies
> >>>>
> >>>> Build: pkg-config ✔
> >>>>
> >>>> Required: gdbm ✔, openssl@1.1 ✔, readline ✔, sqlite ✔, tcl-tk ✔, xz ✔
> >>>>
> >>>> ==> Caveats
> >>>>
> >>>> Python has been installed as
> >>>>
> >>>>   /usr/local/bin/python3
> >>>>
> >>>>
> >>>> Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to
> >>>>
> >>>> `python3`, `python3-config`, `pip3` etc., respectively, have been
> installed into
> >>>>
> >>>>   /usr/local/opt/python@3.9/libexec/bin
> >>>>
> >>>>
> >>>> You can install Python packages with
> >>>>
> >>>>   pip3 install 
> >>>>
> >>>> They will install into the site-package directory
> >>>>
> >>>>   /usr/local/lib/python3.9/site-packages
> >>>>
> >>>>
> >>>> See: https://docs.brew.sh/Homebrew-and-Python
> >>>>
> >>>> ==> Analytics
> >>>>
> >>>> install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
> >>>>
> >>>> install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812
> (365 days)
> >>>>
> >>>> build-error: 0 (30 days)
> >>>>
> >>>>
> >>>> Best Regards,
> >>>>
> >>>> Trevor Karn
> >>>>
> >>>>
> >>>> On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik 
> wrote:
> >>>>>
> >>>>> Could it be that you need to update your Homebrew (?) python3
> package?
> >>>>> What version do you have now?
> >>>>> E.g. on a box where the 

Re: [sage-devel] Trouble building cython

[Trevor Karn]

The only contents of the file you pointed me towards are

__version__ = '0.36.2'

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 9:09 AM Zachary Scherr  wrote:

> I really don't understand.  The Cython log file shows that the problem is
> in
>
>
> /Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/pep425tags.py
>
> I could be mistaken, but I don't think pep425tags.py has been a part of
> the wheel package for a while now.  Certainly when I looked at wheel on my
> sage there was no such file.
>
> Can you go to your
> "/Users/trevorkarn/Applications/sage/local/lib/python3.9/site-packages/wheel/"
> directory and take a look at __init__.py.  Does the version say 0.36.2?
>
> On Monday, February 8, 2021 at 9:32:20 AM UTC-5 Trevor Karn wrote:
>
>>
>> Here is what I get. It seems like it is the same as yours?
>>
>>
>> trevorkarn@Trevors-MacBook-Air sage % brew info python3
>>
>> python@3.9: stable 3.9.1
>>
>> Interpreted, interactive, object-oriented programming language
>>
>> https://www.python.org/
>>
>> /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>>
>>   Built from source on 2021-02-05 at 16:39:31
>>
>> From:
>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>> <https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb>
>>
>> License: Python-2.0
>>
>> ==> *Dependencies*
>>
>> Build: *pkg-config **✔*
>>
>> Required: *gdbm **✔*, *openssl@1.1 **✔*, *readline **✔*, *sqlite **✔*, 
>> *tcl-tk
>> **✔*, *xz **✔*
>>
>> ==> *Caveats*
>>
>> Python has been installed as
>>
>>   /usr/local/bin/python3
>>
>>
>> Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to
>>
>> `python3`, `python3-config`, `pip3` etc., respectively, have been
>> installed into
>>
>>   /usr/local/opt/python@3.9/libexec/bin
>>
>>
>> You can install Python packages with
>>
>>   pip3 install 
>>
>> They will install into the site-package directory
>>
>>   /usr/local/lib/python3.9/site-packages
>>
>>
>> See: https://docs.brew.sh/Homebrew-and-Python
>>
>> ==> *Analytics*
>>
>> install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
>>
>> install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365
>> days)
>>
>> build-error: 0 (30 days)
>>
>> Best Regards,
>>
>> Trevor Karn
>>
>>
>> On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:
>>
>>> Could it be that you need to update your Homebrew (?) python3 package?
>>> What version do you have now?
>>> E.g. on a box where the latest Sage builds I have
>>>
>>> % brew info python3
>>>
>>> python@3.9: stable 3.9.1 (bottled)
>>> Interpreted, interactive, object-oriented programming language
>>> https://www.python.org/
>>> /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>>>   Poured from bottle on 2021-02-06 at 10:13:24
>>> From:
>>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>>> <https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb>
>>>
>>>
>>> On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn  wrote:
>>> >
>>> > Ah I see, thanks for explaining.
>>> >
>>> > Here is my top-level config.log.
>>> >
>>> > Best Regards,
>>> >
>>> > Trevor Karn
>>> >
>>> >
>>> > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik 
>>> wrote:
>>> >>
>>> >>
>>> >>
>>> >> On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:
>>> >>>
>>> >>> Thanks for sending that link. I am confused though, because it says
>>> a fix was issued. Does that mean it should work now?
>>> >>
>>> >>
>>> >> sorry, I was not clear. What I meant to say that it appears to be a
>>> well-known issue in the Python@macOS universe,
>>> >> and lately all seems to be OK with Sage.
>>> >>
>>> >> To figure out exactly goes wrong in your case, we need to know where
>>> Python3 used in Sage is coming from.
>>> >> Please post the top-level config.log
>>> >>
>>> >>
>>> >>>
>>> >>> And yes, I am on the most recent devel

Re: [sage-devel] Trouble building cython

[Trevor Karn]

I also have this. Is there any reason it might be calling python instead of
python3?

trevorkarn@Trevors-MacBook-Air sage % python3 --version

Python 3.9.1

trevorkarn@Trevors-MacBook-Air sage % python --version

Python 2.7.16

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 8:28 AM Trevor Karn  wrote:

>
> Here is what I get. It seems like it is the same as yours?
>
>
> trevorkarn@Trevors-MacBook-Air sage % brew info python3
>
> python@3.9: stable 3.9.1
>
> Interpreted, interactive, object-oriented programming language
>
> https://www.python.org/
>
> /usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *
>
>   Built from source on 2021-02-05 at 16:39:31
>
> From:
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>
> License: Python-2.0
>
> ==> *Dependencies*
>
> Build: *pkg-config **✔*
>
> Required: *gdbm **✔*, *openssl@1.1 **✔*, *readline **✔*, *sqlite **✔*, *tcl-tk
> **✔*, *xz **✔*
>
> ==> *Caveats*
>
> Python has been installed as
>
>   /usr/local/bin/python3
>
>
> Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to
>
> `python3`, `python3-config`, `pip3` etc., respectively, have been
> installed into
>
>   /usr/local/opt/python@3.9/libexec/bin
>
>
> You can install Python packages with
>
>   pip3 install 
>
> They will install into the site-package directory
>
>   /usr/local/lib/python3.9/site-packages
>
>
> See: https://docs.brew.sh/Homebrew-and-Python
>
> ==> *Analytics*
>
> install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)
>
> install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365
> days)
>
> build-error: 0 (30 days)
>
> Best Regards,
>
> Trevor Karn
>
>
> On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:
>
>> Could it be that you need to update your Homebrew (?) python3 package?
>> What version do you have now?
>> E.g. on a box where the latest Sage builds I have
>>
>> % brew info python3
>>
>> python@3.9: stable 3.9.1 (bottled)
>> Interpreted, interactive, object-oriented programming language
>> https://www.python.org/
>> /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>>   Poured from bottle on 2021-02-06 at 10:13:24
>> From:
>> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>>
>>
>> On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn 
>> wrote:
>> >
>> > Ah I see, thanks for explaining.
>> >
>> > Here is my top-level config.log.
>> >
>> > Best Regards,
>> >
>> > Trevor Karn
>> >
>> >
>> > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik 
>> wrote:
>> >>
>> >>
>> >>
>> >> On Mon, 8 Feb 2021, 13:02 Trevor Karn, 
>> wrote:
>> >>>
>> >>> Thanks for sending that link. I am confused though, because it says a
>> fix was issued. Does that mean it should work now?
>> >>
>> >>
>> >> sorry, I was not clear. What I meant to say that it appears to be a
>> well-known issue in the Python@macOS universe,
>> >> and lately all seems to be OK with Sage.
>> >>
>> >> To figure out exactly goes wrong in your case, we need to know where
>> Python3 used in Sage is coming from.
>> >> Please post the top-level config.log
>> >>
>> >>
>> >>>
>> >>> And yes, I am on the most recent develop branch
>> >>>
>> >>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik 
>> wrote:
>> >>>>
>> >>>> This seems to be well-known issue, see e.g
>> >>>> https://github.com/pypa/virtualenv/issues/2027
>> >>>>
>> >>>> Are you on the most recent develop branch (9.3.beta7)?
>> >>>>
>> >>>> On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn 
>> wrote:
>> >>>> >
>> >>>> > Hi,
>> >>>> >
>> >>>> > I'm trying to build Sage from the source code. I cloned it from
>> git, and tried to build from the develop branch using make from the sage
>> directory. I ran into trouble building cython. The error message suggested
>> that I email this group. Does anyone have any advice on how to proceed?
>> >>>> >
>> >>>> > I am using macOS Big Sur 11.2 on a MacBook Air.
>> >>>> >
>> >>>> > The log file is attached, this is from a second run - it failed
>

Re: [sage-devel] Trouble building cython

[Trevor Karn]

Here is what I get. It seems like it is the same as yours?


trevorkarn@Trevors-MacBook-Air sage % brew info python3

python@3.9: stable 3.9.1

Interpreted, interactive, object-oriented programming language

https://www.python.org/

/usr/local/Cellar/python@3.9/3.9.1_8 (8,665 files, 129.4MB) *

  Built from source on 2021-02-05 at 16:39:31

From:
https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb

License: Python-2.0

==> *Dependencies*

Build: *pkg-config **✔*

Required: *gdbm **✔*, *openssl@1.1 **✔*, *readline **✔*, *sqlite **✔*, *tcl-tk
**✔*, *xz **✔*

==> *Caveats*

Python has been installed as

  /usr/local/bin/python3


Unversioned symlinks `python`, `python-config`, `pip` etc. pointing to

`python3`, `python3-config`, `pip3` etc., respectively, have been installed
into

  /usr/local/opt/python@3.9/libexec/bin


You can install Python packages with

  pip3 install 

They will install into the site-package directory

  /usr/local/lib/python3.9/site-packages


See: https://docs.brew.sh/Homebrew-and-Python

==> *Analytics*

install: 755,419 (30 days), 2,396,024 (90 days), 2,995,387 (365 days)

install-on-request: 244,063 (30 days), 714,665 (90 days), 799,812 (365 days)

build-error: 0 (30 days)

Best Regards,

Trevor Karn


On Mon, Feb 8, 2021 at 8:17 AM Dima Pasechnik  wrote:

> Could it be that you need to update your Homebrew (?) python3 package?
> What version do you have now?
> E.g. on a box where the latest Sage builds I have
>
> % brew info python3
>
> python@3.9: stable 3.9.1 (bottled)
> Interpreted, interactive, object-oriented programming language
> https://www.python.org/
> /usr/local/Cellar/python@3.9/3.9.1_8 (4,057 files, 67.8MB) *
>   Poured from bottle on 2021-02-06 at 10:13:24
> From:
> https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/pyt...@3.9.rb
>
>
> On Mon, Feb 8, 2021 at 1:53 PM Trevor Karn 
> wrote:
> >
> > Ah I see, thanks for explaining.
> >
> > Here is my top-level config.log.
> >
> > Best Regards,
> >
> > Trevor Karn
> >
> >
> > On Mon, Feb 8, 2021 at 7:09 AM Dima Pasechnik  wrote:
> >>
> >>
> >>
> >> On Mon, 8 Feb 2021, 13:02 Trevor Karn,  wrote:
> >>>
> >>> Thanks for sending that link. I am confused though, because it says a
> fix was issued. Does that mean it should work now?
> >>
> >>
> >> sorry, I was not clear. What I meant to say that it appears to be a
> well-known issue in the Python@macOS universe,
> >> and lately all seems to be OK with Sage.
> >>
> >> To figure out exactly goes wrong in your case, we need to know where
> Python3 used in Sage is coming from.
> >> Please post the top-level config.log
> >>
> >>
> >>>
> >>> And yes, I am on the most recent develop branch
> >>>
> >>> On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik 
> wrote:
> >>>>
> >>>> This seems to be well-known issue, see e.g
> >>>> https://github.com/pypa/virtualenv/issues/2027
> >>>>
> >>>> Are you on the most recent develop branch (9.3.beta7)?
> >>>>
> >>>> On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn 
> wrote:
> >>>> >
> >>>> > Hi,
> >>>> >
> >>>> > I'm trying to build Sage from the source code. I cloned it from
> git, and tried to build from the develop branch using make from the sage
> directory. I ran into trouble building cython. The error message suggested
> that I email this group. Does anyone have any advice on how to proceed?
> >>>> >
> >>>> > I am using macOS Big Sur 11.2 on a MacBook Air.
> >>>> >
> >>>> > The log file is attached, this is from a second run - it failed
> once, and I tried running make a second time without any changes and this
> is the log from the second run, which returns the same error just without
> all of the info before it (eg. the flint installation).
> >>>> >
> >>>> > Thanks so much.
> >>>> >
> >>>> > Best,
> >>>> > Trevor
> >>>> >
> >>>> > --
> >>>> > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/1c93ec2e-86bd-45f0-bba0-cc254a392305n%40googlegroups.com
> .
> 

Re: [sage-devel] Trouble building cython

[Trevor Karn]

Thanks for sending that link. I am confused though, because it says a fix
was issued. Does that mean it should work now?

And yes, I am on the most recent develop branch

On Mon, Feb 8, 2021 at 5:42 AM Dima Pasechnik  wrote:

> This seems to be well-known issue, see e.g
> https://github.com/pypa/virtualenv/issues/2027
>
> Are you on the most recent develop branch (9.3.beta7)?
>
> On Mon, Feb 8, 2021 at 9:20 AM Trevor Karn 
> wrote:
> >
> > Hi,
> >
> > I'm trying to build Sage from the source code. I cloned it from git, and
> tried to build from the develop branch using make from the sage directory.
> I ran into trouble building cython. The error message suggested that I
> email this group. Does anyone have any advice on how to proceed?
> >
> > I am using macOS Big Sur 11.2 on a MacBook Air.
> >
> > The log file is attached, this is from a second run - it failed once,
> and I tried running make a second time without any changes and this is the
> log from the second run, which returns the same error just without all of
> the info before it (eg. the flint installation).
> >
> > Thanks so much.
> >
> > Best,
> > Trevor
> >
> > --
> > 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/1c93ec2e-86bd-45f0-bba0-cc254a392305n%40googlegroups.com
> .
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "sage-devel" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/sage-devel/TmbLnmwz2mg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAAWYfq3CFFAYzUtNnSrt_RPKW7X_p8j_VXGtZbKLWG%2BST%3DCO%2BQ%40mail.gmail.com
> .
>
-- 
Best,

Trevor

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAJ6VCMAVGG57CHovd7zoXa0C3Nxsr3WfXi0FWwapKrDfup7_sA%40mail.gmail.com.