Nicholas Cole added the comment:
I've just tried the OS X build of 3.3rc2, and this has been fixed. Thank you!
--
___
Python tracker
<http://bugs.python.org/is
Nicholas Cole added the comment:
On Mon, Sep 3, 2012 at 3:15 PM, STINNER Victor wrote:
>
> STINNER Victor added the comment:
>
>> How do I check which version it was built against?
>
> On Linux, I use:
>
> $ ldd /usr/lib/python2.7/lib-dynload/_curses.so |grep curses
Nicholas Cole added the comment:
> Unless I'm getting the build process wrong (possible, because
> I haven't tried testing fixes before), this fix isn't working for me.
Oh did you compile Python? Did you install it?
Yes, I tried compiling it.
#./configure MACOSX_D
Nicholas Cole added the comment:
Unless I'm getting the build process wrong (possible, because I haven't tried
testing fixes before), this fix isn't working for me.
--
___
Python tracker
<http://bugs.pyt
Nicholas Cole added the comment:
import curses
def test_screen(screen):
screen.addch(5,5, curses.ACS_HLINE)
screen.addch(5,6, curses.ACS_HLINE)
screen.refresh()
curses.napms(2000)
curses.wrapper(test_screen)
--
___
Python tracker
Nicholas Cole added the comment:
I'm reopening this bug because I've noticed that in Python3.3rc1, although
trying to print curses.ACS_HLINE and other such characters no long cause an
Exception, only blank characters are printed to the screen.
Tested with both Terminal.App and xte
Nicholas Cole added the comment:
Testing the Python3.3a2 build on OS X - the exception
AttributeError: '_curses.curses window' object has no attribute 'get_wch'
is still being raised. I don't have a Linux build I can easily test with. Is
this a particular pr
Nicholas Cole added the comment:
Poq: I agree. Guessing from the Unicode standard is going to lead to users
having to write some complicated code that people are going have to reinvent
over and over, and is not going to be accurate with respect to curses. I'd
favour exposing wc
Nicholas Cole added the comment:
Marting and Poq: I think the sample code shows up a real problem. "Ambiguous"
characters according to unicode may be rendered by curses in different ways.
Don't we need a function that actually reports how curses is going to print a
given stri
Nicholas Cole added the comment:
Martin: sorry to be completely dense, but I can't get this to work properly
with the python3.3a1 build. Could you post some example code?
--
___
Python tracker
<http://bugs.python.org/is
Nicholas Cole added the comment:
Could we have an update on the status of this? I ask because if 3.3 is going to
(finally) fix unicode for curses, it would be really nice if it were possible
to calculate the width of what's being displayed! It looks as if there was
never quite agreeme
Nicholas Cole added the comment:
On Wed, Mar 7, 2012 at 7:40 AM, R. David Murray wrote:
>
> R. David Murray added the comment:
>
> Since this bug is about adding a new feature, it is unlikely to be the
> correct bug for this to be against.
>
> Given that you've
New submission from Nicholas Cole :
The following code works on Python versions prior to 3.3a1:
import curses
def test_screen(screen):
screen.addch(5,5, curses.ACS_HLINE)
screen.refresh()
curses.wrapper(test_screen)
On python3.3, the program produces the following traceback
Nicholas Cole added the comment:
I hope that this is the right bug to file this on (I'm getting lost in all of
the curses bugs!).
I'm testing out the 3.3a1, and I've run into the following issue. On previous
releases addch() could accept curses.ACS_HLINE and similar.
Attemp
Nicholas Cole added the comment:
It looks to me as if the documentation in the release candidates for 2.7.3 and
3.2.3 haven't been updated to include the new curses fixes. Is that correct?
--
___
Python tracker
<http://bugs.python.org/is
Nicholas Cole added the comment:
There are now several bugs dealing with related issues here. Are we any closer
to a solution to any of them? The suggested patches look like a good idea -
what needs to happen for them to move forward
Nicholas Cole added the comment:
I think that some platforms do not have wide character support, though I could
be wrong. The FAQ here: http://invisible-island.net/ncurses/ncurses.faq.html
has a list of those that do and those that don't, but I don't know how up to
Nicholas Cole added the comment:
> Nobody wanted to take the responsability of the choice for get_wch(): add a
> new method or patch getch() ;-)
I suspect that a new method is the right way to go, here.
I see it has been moved to "committed/rejected" status - does that mea
Changes by Nicholas Cole :
--
nosy: +Nicholas.Cole
___
Python tracker
<http://bugs.python.org/issue12568>
___
___
Python-bugs-list mailing list
Unsubscribe:
Nicholas Cole added the comment:
The bug is marked "Test Needed".
I am very keen to see this issue fixed, and would be very willing to help, but
I don't really know what is still required. As far as I can see there is a
patch waiting - what
Nicholas Cole added the comment:
Is there any hope that something like this patch will make it into a future
version? As far as I can see, entering accented characters is currently
impossible on the latest release versions of python...or am I missing something?
--
nosy
21 matches
Mail list logo
