A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2000-December/010968.html below:

[Python-Dev] Splitting up _cursesmodule

[Python-Dev] Splitting up _cursesmoduleAndrew Kuchling akuchlin@mems-exchange.org
Wed, 13 Dec 2000 07:44:23 -0500
[CC'ing Thomas Gellekum <tg@melaten.rwth-aachen.de>]

On Wed, Dec 13, 2000 at 01:24:01AM -0500, Fred L. Drake, Jr. wrote:
>  Would it be reasonable to add panel support as a second extension
>module?  Is there really a need for them to be in the same module,
>since the panel library is a separate library?

Quite possibly, though the patch isn't structured that way.  The panel
module will need access to the type object for the curses window
object, so it'll have to ensure that _curses is already imported, but
that's no problem.

Thomas, do you feel capable of implementing it as a separate module,
or should I work on it?  Probably a _cursesmodule.h header will have
to be created to make various definitions available to external users
of the basic objects in _curses.  (Bonus: this means that the menu and
form libraries, if they ever get wrapped, can be separate modules, too.)

--amk




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4