Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AsymptoticRing: convert Orders of symbolic ring #19426

Open
dkrenn opened this issue Oct 16, 2015 · 14 comments
Open

AsymptoticRing: convert Orders of symbolic ring #19426

dkrenn opened this issue Oct 16, 2015 · 14 comments

Comments

@dkrenn
Copy link
Contributor

dkrenn commented Oct 16, 2015

Implement conversion from Order(...) to asymptotic rings.

(There seems to be a bug in SR (#19425) which has to be solved first.)

Depends on #19083
Depends on #19425

CC: @behackl

Component: asymptotic expansions

Work Issues: rebase

Author: Eran Assaf

Branch/Commit: u/assaferan/asymptoticring__convert_orders_of_symbolic_ring @ 90152f3

Reviewer: Benjamin Hackl

Issue created by migration from https://trac.sagemath.org/ticket/19426

@cheuberg

This comment has been minimized.

@cheuberg
Copy link
Contributor

Changed dependencies from #19083, #19424 to #19083, #19425

@assaferan
Copy link
Mannequin

assaferan mannequin commented Mar 11, 2018

@assaferan
Copy link
Mannequin

assaferan mannequin commented Mar 11, 2018

New commits:

bd4a461Changed brial installation to support cygwin 64-bit with the new limits.h
60c5606Fixed Ticket #19426 - Implemented conversion from Order(...) to asymptotic rings.
cd2f1a4Added conversion from Symbolic Order to Asymptotic Ring.
45ec3d7Added an appropriate doctest

@assaferan
Copy link
Mannequin

assaferan mannequin commented Mar 11, 2018

Author: Eran Assaf

@assaferan
Copy link
Mannequin

assaferan mannequin commented Mar 11, 2018

Commit: 45ec3d7

@assaferan assaferan mannequin added the s: needs review label Mar 11, 2018
@behackl
Copy link
Member

behackl commented Mar 11, 2018

Reviewer: Benjamin Hackl

@behackl
Copy link
Member

behackl commented Mar 11, 2018

comment:6

Hi! Your basic approach looks good, however, you should merge the latest beta (8.2.beta8) into your branch and fix the resulting merge conflict with your adaption of the brial configuration. (This issue has been fixed in #24860, which is merged in beta8.)

As a suggestion: you should keep fixes for unrelated problems (like in this case the brial problem) separate from the code for this ticket (basically, separate fixes deserve separate tickets).

I'll review this as soon as the conflict is resolved.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Mar 11, 2018

Branch pushed to git repo; I updated commit sha1. New commits:

90152f3merged latest beta code with mine

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Mar 11, 2018

Changed commit from 45ec3d7 to 90152f3

@assaferan
Copy link
Mannequin

assaferan mannequin commented Mar 11, 2018

comment:8

Hi!
I've fixed the conflict and committed the changes.

In principal, I agree with your suggestion. The problem was I could not build sage on my PC without fixing this problem, and it took a while until I could get everything to work (trac user, git, etc.).

Anyway, hopefully it can be reviewed now.
Thanks,
Eran

@assaferan assaferan mannequin added s: needs review and removed s: needs work labels Mar 11, 2018
@RelationaleDB
Copy link
Mannequin

RelationaleDB mannequin commented Jul 26, 2019

comment:9

merge conflict

@RelationaleDB
Copy link
Mannequin

RelationaleDB mannequin commented Jul 26, 2019

Work Issues: rebase

@DaveWitteMorris
Copy link
Member

comment:10

Removing the "beginner" tag from old tickets. Some could be returned to beginner-friendly status by adding a comment about what needs to be done. Some others might be easy for an experienced developer to finish.

@mkoeppe mkoeppe removed this from the sage-8.2 milestone Dec 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants