On Sun, Aug 7, 2011 at 1:23 AM, Aaron Meurer <[email protected]> wrote:
> I implemented the preliminary version of this in my wrap branch.
> There are still a few things to do (see the TODO in the commit
> message). I will go ahead and open a pull request for it, though you
> might hold off on actually merging it until I am completely finished.
>
> And regarding unicode, it is possible to tell if a terminal supports
> unicode or not (I'll see what SymPy does, or maybe urwid has something
> built in). I think I will use that.
>
> Aaron Meurer
>
urwid.util.detected_encoding returns the encoding of the terminal as
given by the locale module ("UTF-8" if unicode is supported).
However, this is behaving very strangely.
If I set the last character to … (the unicode character), it just puts
a ?. If I set the second to last character to …, it makes that and
also the last character ?. But if I set the third to last character to
…, it works.
I am going to push up a change to my wrap branch that adds ... (three
dots), and that has the other code there but disabled so you can test
it.
I can see now what everyone is talking about with unicode in Python 2.
Aaron Meurer
> On Tue, Aug 2, 2011 at 7:41 AM, Andreas Kloeckner
> <[email protected]> wrote:
>> On Mon, 1 Aug 2011 18:31:20 -0600, Aaron Meurer <[email protected]> wrote:
>>> So PuDB requires a unicode terminal?
>>
>> I suppose not. I guess that was a bad idea.
>>
>> Andreas
>>
>>
>
_______________________________________________
Pudb mailing list
[email protected]
http://lists.tiker.net/listinfo/pudb
