Hi Jori,

On 2015-10-05, Jori =?ISO-8859-1?Q?M=E4ntysalo?= <jori.mantys...@uta.fi> wrote:
> Also this does not work with all (longer?) functions in the notebook. Try
>
> g = Graph()
> g.plot??
>
> for an example of one kind of a bug.

Works for me (on the command line at least). At some point, the notebook
code duplicated the relevant code in sage.misc.sageinspect and did *not*
keep up with the bugfixes. If it only happens in the notebook then
that's the likely cause.

> And of course it might be tricky to follow the code. For example
>
> P = Poset()
> P.mobius_function??
>
> basically shows that you must look from the code of Hasse diagram. So you 
> continue with
>
> P._hasse_diagram.mobius_function??
>
> and see the function? Yes and no. If you say
>
> P = Poset()
> P.mobius_function_matrix()
> P.mobius_function??
>
> you see how it was redefined when you computed the matrix. You can not 
> know that before trying or reading source code for few .py files.

That's not a bug, because you see the source code. Admittedly I don't
like that in *some* parts of Sage the source code is full of
indirections and aliases.

Best regards,
Simon


-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to