Disabled _curses modules on MacOSX. The curses version is a 1994 BSD curses, far too old for _cursesmodule.c.
But what if someone installs their own, better version of curses, e.g. in /usr/local? Maybe you should only disable it if it's darwin *and* if it's in a standard location? Or if the header file contains a certain characteristic string?
This is probably a good idea, but I know absolutely nothing about curses, so someone else will have to do this (I think the standard location trick isn't good enough, Apple could supply a more decent curses in a next release, so it'll have to be the string trick). And actually I don't _want_ to know anything about curses, really:-)
Maybe you can reopen the bug and assign it to someone who uses curses? I think the bug isn't OSX specific, I would be very surprised if other FreeBSD's at least don't have the same problem (why would Apple take FreeBSD but put an older version of curses in, after all). -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm