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.

Sign up for GitHub

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

Jump to bottom

Bug in parsing Maxima output with factorial #14352

Closed
eviatarbach opened this issue Mar 24, 2013 · 5 comments
Closed

Bug in parsing Maxima output with factorial #14352

eviatarbach opened this issue Mar 24, 2013 · 5 comments
Assignees
@burcin
Labels
c: symbolics r: duplicate t: bug

Comments

@eviatarbach
Copy link

Sage interprets the Maxima factorial operator as the inequality symbol in some cases:

sage: factorial(x) == 6                                                   
factorial(x) == 6
sage: _.simplify()
x != 6

I set the priority to critical because this can produce wrong answers. For example,

bool((factorial(x) == 6).simplify().subs(x=2))

CC: @kcrisman

Component: symbolics

Reviewer: Eviatar Bach, Karl-Dieter Crisman

Issue created by migration from https://trac.sagemath.org/ticket/14352
@eviatarbach eviatarbach added this to the sage-5.9 milestone Mar 24, 2013
@eviatarbach

This comment has been minimized.

Sign in to view
@eviatarbach
Copy link
Author

comment:2

Maxima uses # for inequality, so ! should never be interpreted as such.

@kcrisman
Copy link
Member

comment:3

I think this is a duplicate of #11539. Do you agree?

@kcrisman kcrisman removed this from the sage-5.9 milestone Mar 25, 2013
@eviatarbach
Copy link
Author

comment:4

Ah yes. I had even commented on that one, totally forgot about it...

@kcrisman
Copy link
Member

Reviewer: Eviatar Bach, Karl-Dieter Crisman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@burcin burcin

Labels
c: symbolics r: duplicate t: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@burcin @eviatarbach @kcrisman @jdemeyer