[sage-devel] Re: issue with division in fraction field of univ poly

2023-07-02 Thread 'Travis Scrimshaw' via sage-devel
When I first tried Ben's OP code, it worked as there. Then when trying Nil's code, I get the same output as Ben, but when I immediate after run sage: D2 / D1 ...Same traceback as above... ZeroDivisionError: fraction field element division by zero Now in a fresh Sage session, I immediately get

[sage-devel] Re: New package creation - advice/help requested

2023-07-02 Thread 'Travis Scrimshaw' via sage-devel
Hi Aram, Can you explain a bit more why you aren't just integrating it into Sage now? Are you're expecting to have major API changes? There would likely be a push to change to using more Cython, but it doesn't need to be feature complete to be a part of Sage and internal/implementation

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

2023-07-02 Thread 'Travis Scrimshaw' via sage-devel
(A) Travis On Monday, July 3, 2023 at 2:42:10 AM UTC+9 G. M.-S. wrote: > > My choice is (A). > > Guillermo > > On Thu, 29 Jun 2023 at 04:40, Kwankyu Lee wrote: > >> Hi, >> >> We spent six days for the preliminary discussion in the sage-devel thread >> >>

Re: [sage-devel] Re: Ask about the SageMath codebase using ChatGPT

2023-07-02 Thread 'Martin R' via sage-devel
It is very much hallucinating. Worse, it seems that it does not know the sage codebase very well, since sage has actually some dedicated tools helping with the question - in the case at hand, oeis, findstat and Bijectionist come to mind. Is there a fundamental reason it does not know them?

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

2023-07-02 Thread G. M.-S.
My choice is (A). Guillermo On Thu, 29 Jun 2023 at 04:40, Kwankyu Lee wrote: > Hi, > > We spent six days for the preliminary discussion in the sage-devel thread > > https://groups.google.com/g/sage-devel/c/OUnoroIf0qc > > about choosing the keyword triggering block-scoped optional tag needed

Re: [sage-devel] Should I report codepaths leading to comparing incomparable objects?

2023-07-02 Thread Georgi Guninski
You definitely can construct graph with incomparable vertices and they worked as expected in python2. python3 regressed them and devs are doing workarounds. The new testace is: G=Graph([("A",1)]) G.feedback_vertex_set() === File /home/sc_serv/sage/src/sage/graphs/connectivity.pyx:287, in

Re: [sage-devel] Should I report codepaths leading to comparing incomparable objects?

2023-07-02 Thread Dima Pasechnik
On Sun, Jul 2, 2023 at 4:59 PM Georgi Guninski wrote: > > I reported several bugs about Graph.vertices() and have > the impression that sage devs are aware of the problem and > don't want bug reports about this. What was the problem there? IMHO that was working as expected - you cannot build

[sage-devel] Should I report codepaths leading to comparing incomparable objects?

2023-07-02 Thread Georgi Guninski
I reported several bugs about Graph.vertices() and have the impression that sage devs are aware of the problem and don't want bug reports about this. I have another testcase not related to vertices(), should I report it? -- You received this message because you are subscribed to the Google