#3342: [with spkg, needs work] bizarre source code introspection output
---------------------------+------------------------------------------------
 Reporter:  was            |       Owner:  tba       
     Type:  defect         |      Status:  new       
 Priority:  minor          |   Milestone:  sage-4.1.1
Component:  documentation  |    Keywords:            
 Reviewer:                 |      Author:            
   Merged:                 |  
---------------------------+------------------------------------------------

Comment(by wjp):

 I think this patch is not the right way to approach this. Maybe replacing
 the {{{write}}} in {{{out.write(header('Source:\n')+source.rstrip())}}} by
 {{{writeln}}} is a cleaner approach. I'd feel a lot more confident about
 changing that if I would understand why some of the writes in the
 {{{pinfo}}} function use {{{write}}} while others use {{{writeln}}},
 though...

 Another thing is that this particular class docstring "<attribute
 '__doc__' of 'builtin_function_or_method' objects>" looks like a good
 candidate for inclusion in the "Skip Python's auto-generated docstring"
 list in that function, because it doesn't seem to add much (if any) useful
 information.
 (That seems to be caused by it being in a Cython class, which is probably
 why IPython doesn't already list it.)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/3342#comment:4>
Sage <http://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