#6111: [with patch; needs review] review symbolics in sage-4.0 (switch to pynac)
----------------------+-----------------------------------------------------
 Reporter:  was       |       Owner:  burcin  
     Type:  defect    |      Status:  new     
 Priority:  blocker   |   Milestone:  sage-4.0
Component:  calculus  |    Keywords:          
----------------------+-----------------------------------------------------

Comment(by burcin):

 Some comments after reading the changesets to pynac after the unreleased
 0.1.6 version (numbers next to the bullets refer to changesets in the
 repository from the pynac-0.1.7.spkg file):


  * 90:fb6582f9bd81

  isn't this already handled by the first lines of pyExpression_to_ex() in
 pynac.pyx?
  * 88:25d02eeb427d

  we should add error checking to py_get_constant() call, we can't
 guarantee that a constant with the same name will be available between
 different versions of Sage
  * 84:7b3272f4b4bf  is mine, author field lists Mike
  * 82:da7d7a220723  evalf for constants using a lookup table

  I already commented on this on IRC and the devel list. ginac/pynac
 already provides a framework to handle this, I would like to revert this
 in a future version. My previous message:
  http://groups.google.com/group/sage-devel/msg/dc46d9d94dd31b5e (scroll to
 the paragraph below the bullet items)

 I will try to prepare a new package which fixes the version numbers of the
 library and error handling of py_get_constant().

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6111#comment:5>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to