GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [Python-Dev] Splitting up _cursesmodule
  • [Python-Dev] Splitting up _cursesmodule
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Splitting up _cursesmodule

[Python-Dev] Splitting up _cursesmodule

Thomas Gellekum [email protected]
14 Dec 2000 14:07:12 +0100

  • Previous message: [Python-Dev] Splitting up _cursesmodule
  • Next message: [Python-Dev] Splitting up _cursesmodule
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Andrew Kuchling <[email protected]> writes:

> I'm ambivalent about the list_of_panels.  It's a linked list storing
> (PyWindow, PyPanel) pairs.  Probably it should use a dictionary
> instead of implementing a little list, just to reduce the amount of
> code.

I don't like it either, so feel free to shred it. As I said, this is
the first (piece of an) extension module I've written and I thought it
would be easier to implement a little list than to manage a Python
list or such in C.

> So, I suggest we create _curses_panel.c, which would be available as
> curses.panel.  (A panel.py module could then add any convenience
> functions that are required.)
> 
> Thomas, do you want to work on this, or should I?

Just do it. I'll try to add more examples in the meantime.

tg



  • Previous message: [Python-Dev] Splitting up _cursesmodule
  • Next message: [Python-Dev] Splitting up _cursesmodule
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.