Apparently the string/char handling has been updated in Python 3:

> ord('')
TypeError: ord() expected a character, but string of length 0 found

On Feb 20, 2013, at 2:41 PM, Martin Grund <notifications@github.com> wrote:

> In sbp_kill_ring.py:
> 
> > @@ -27,7 +27,7 @@ def atEOL(cls, view, point):
> >      @classmethod
> >      def atEOF(cls, view, point):
> >          nextChar = view.substr(point)
> > -        return ord(nextChar) == 0
> > +        return nextChar == ""
> Shouldn't the ordinal value of both be 0? independent of unicode or not?
> 
> —
> Reply to this email directly or view it on GitHub.
> 
>