#11415: update pynac to 0.2.3
----------------------------------------------------+-----------------------
   Reporter:  burcin                                |          Owner:  burcin   
                                    
       Type:  defect                                |         Status:  
positive_review                              
   Priority:  major                                 |      Milestone:  
sage-4.7.1                                   
  Component:  symbolics                             |       Keywords:           
                                    
Work_issues:                                        |       Upstream:  N/A      
                                    
   Reviewer:  Karl-Dieter Crisman, François Bissey  |         Author:  Richard 
Kreckel, Jens Vollinga, Burcin Erocal
     Merged:                                        |   Dependencies:           
                                    
----------------------------------------------------+-----------------------

Comment(by burcin):

 Replying to [comment:7 fbissey]:
 > I actually didn't report all the warnings. Just the easy to fix one.
 There's some of that as well:
  {{{
  /scratch/portage/sci-
 libs/pynac-0.2.2/work/pynac-0.2.2/src/ginac/numeric.cpp: In function
 'PyObject* Integer(const long int&)':
  /scratch/portage/sci-
 libs/pynac-0.2.2/work/pynac-0.2.2/src/ginac/numeric.cpp:173:56: warning:
 deprecated conversion from string constant to 'char*'
  /scratch/portage/sci-
 libs/pynac-0.2.2/work/pynac-0.2.2/src/ginac/numeric.cpp: In function 'void
 GiNaC::coerce(GiNaC::Number_T&, GiNaC::Number_T&, const GiNaC::Number_T&,
 const GiNaC::Number_T&)':
  /scratch/portage/sci-
 libs/pynac-0.2.2/work/pynac-0.2.2/src/ginac/numeric.cpp:262:67: warning:
 deprecated conversion from string constant to 'char*'
  }}}
 > But you wouldn't believe how widespread this one is. Just look at your
 singular build logs for example when you have time.
 > I may attempt your other question but in #9240 (he says looking at his C
 manual and looking at the code).

 I try to fix the warnings I know about. Thanks Francois for reporting the
 `%lf` issue.

 Unfortunately the ones above are due to the python headers not declaring
 the `char*` arguments of some functions as const. I don't think it's a
 good idea to manually cast to a nonconstant type to suppress these
 warnings.


 Many thanks for the reviews Karl-Dieter.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11415#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
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