On Jun 24, 2:10 am, Volker Braun <vbraun.n...@gmail.com> wrote:
> On Sunday, June 24, 2012 9:45:34 AM UTC+1, Simon King wrote:
>
> > Shouldn't we rather duck typing?
>
> Ideally, yes. So an even better solution would be
>
> try:
> X = range(1,X+1)
> except TypeError:
> pass
Isn't that the wrong way around? The documentation of the function
shows that primarily, X is supposed to be an iterable (list) of
coefficient indices. It accepts an integer as abbreviation for
range(1,X+1). So, duck typing would suggest that this is only tried if
X fails to be an iterable. You'd notice the difference if you'd feed
in a type that is iterable AND can be turned into an integer.
Something along the lines of:
try:
X = iter(X)
except TypeError:
try:
X = iter(xrange(1,X+1))
except TypeError:
raise TypeError("'%o' object is neither iterable nor can be
turned into an integer"%type(X))
might be a little more robust in the face of unexpected input types.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
