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

pynac -- add _polynomial_ conversion constructor #5763

Closed
ncalexan mannequin opened this issue Apr 11, 2009 · 7 comments
Closed

pynac -- add _polynomial_ conversion constructor #5763

ncalexan mannequin opened this issue Apr 11, 2009 · 7 comments

Comments

@ncalexan
Copy link
Mannequin

ncalexan mannequin commented Apr 11, 2009

The attached patch adds conversion to polynomial rings. Two doctests fail at this time; they rely on being able to convert to CDF and ComplexField(100). I didn't want them to get forgotten so I left them in.

CC: @burcin @mwhansen @williamstein

Component: symbolics

Keywords: pynac symbolics polynomial constructor

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

@ncalexan ncalexan mannequin added this to the sage-4.0.1 milestone Apr 11, 2009
@ncalexan ncalexan mannequin added c: symbolics labels Apr 11, 2009
@burcin
Copy link

burcin commented Apr 12, 2009

comment:1

Attachment: trac_5763-symbolic-polynomial.patch.gz

Thanks Nick!

The patch looks great, I am looking at the doctests right now.

Note that #5753 fixes the coercion of constants to pynac, so you can use is_a_constant in the .is_constant() function.

I will see what I can do about the doctest failures, and hopefully post a patch fixing them soon.

@ncalexan
Copy link
Mannequin Author

ncalexan mannequin commented Apr 12, 2009

comment:2

In fact, you can make the doctest works by changing the if is_constant check to coerce the pyobject in. It's a one line fix that I haven't posted here, it works well for me in practice.

@burcin
Copy link

burcin commented May 24, 2009

comment:3

This patch seems to have been forgotten during the "pynac push." I recall that it was briefly mentioned on IRC once.

I suggest closing this issue as wontfix now. Trac doesn't allow me close tickets any more.

@burcin burcin modified the milestones: sage-4.0.1, sage-4.0 May 24, 2009
@williamstein
Copy link
Contributor

comment:4

This isn't critical for 4.0.

@williamstein williamstein modified the milestones: sage-4.0, sage-4.0.1 May 28, 2009
@sagetrac-mvngu
Copy link
Mannequin

sagetrac-mvngu mannequin commented Jun 8, 2009

comment:5

The docstring should adhere to ReST formatting. Some examples follow this rule, but most don't. I'm merely enforcing proper ReST formatting, not actually reviewing the whole patch.

@boothby
Copy link

boothby commented Jul 15, 2009

comment:6

This should have been marked as a negative review.

@mwhansen
Copy link
Contributor

comment:7

I think we can close this as invalid as all of the doctests in the patch currenly pass.

@mwhansen mwhansen removed this from the sage-5.11 milestone Jul 22, 2013
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

4 participants