Thanks for these clear explanations. The case of IPython tab mechanism for getting documentation is very convincing!
Coming from the C++ world, I was used to have the attributes private, but was not sure about the Python way of dealing with this (having read different opinions about it). I did not underscored the "light" attributes, like tensor_type, as noticed by Volker, to avoid the cost of calling some method tensor_type() (in C++, thanks to the inline mechanism, there is no cost issue for such access methods). But I am fully convinced now and I am turning all the attributes of SageManifolds classes to private and introduce the corresponding access methods, with their docstrings. Eric. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
