+1 to everything Johan is writing. I think that the example B.I.roo<tab>
that hangs forever (or almost) is particularly striking.
As an aside, I agree that deprecation has a cost, and this observation
shows up in several discussions these days on sage-devel. For general
changes, like deprecate the use of properties for the end user, or
change the way packages can be installed, etc., we may take the
opportunity of the future switch from Python 2 to Python 3 to implement
them. Thus we could then advertise that from version 10.0 (say), the
interface of Sage changes (in a backward incompatible manner, due in
particular to Py2>Py3). If this comes together with a clear document,
easily found on sagemath.org, etc. that explains all the changes, it
would minimize the pain caused to the users.
Bruno
Le 27/04/2016 14:24, Johan S. R. Nielsen a écrit :
VulK writes:
sage: B = matrix()
sage: B.T.roo<Tab>
and get
sage: B.T.rook_vector
I see, didn't know that.
Of course, the reason that IDEs follow this is the underlying convention
that
a) Properties are blazingly fast to compute.
b) Properties don't throw exceptions.
Neither of which are satisfied for Matrix.I. If B is a 1000x1000
matrix over ZZ(x), then B.I.roo<Tab> is going to hang your IDE for a
while :-)
Best,
Johan
--
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 https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
