Update: I found a way to check for the exact exception reported, which
was common to the Sprox failure and other unsliceable failures
("TypeError: unhashable type"). So I can at least raise the
incompatible message so users will know what's going on.On Tue, Mar 22, 2011 at 10:21 PM, Mike Orr <sluggos...@gmail.com> wrote: > I changed the .__slice__ to .__getitem__. This passes the tests in the > SQLAlchemy and sliceable cases. I think it will let some non-sliceable > cases through which would cause the original Sprox error, but i don't > think there's anything we can do about that because we can't check > whether .__getitem__ accepts a slice without calling it and guessing > what the exception means, and calling it may cause side effects (like > a db query). > > So if y'all can make sure you're satisfied with it, I'll release beta > 2 in a day or two. > > -- > Mike Orr <sluggos...@gmail.com> > -- Mike Orr <sluggos...@gmail.com> -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To post to this group, send email to pylons-devel@googlegroups.com. To unsubscribe from this group, send email to pylons-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pylons-devel?hl=en.
