Not sure what to set theType field to, this is my first patch 
submission.  The attached files are a unit test 
test_curses_color_set.py and the diff color_set_diff, apparently I can 
only attach one fo thetwo files.

Why was this classified as "documentation"?

According to the python.org website: http://python.org/dev/patches/

We were to submit Documentation patches as Documentation, but it did'nt
say what to submit other types of patches as, so I took a chance.

How should it have been submitted?

Best Regards,
Steve Owens
>
> Georg Brandl <georg@python.org> added the comment:
>
> Why was this classified as "documentation"?
>
> ----------
> components: +Extension Modules -Documentation
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue5368>
> _______________________________________
>

I have also added the addchstr family of functions.  The updated patch2
should include the previos patch since it has not been applied to the
repository as of this writing.  See also the unittest for the addchstr
method family.

I will update the docs and add those as well, but there is quite alot of
documentation that needs to be done and it is late, please let me know
if this will be an acceptable patch. I'm still new.

This is the addchstr unit test.

This is a start on the documentation efforts.  I have updated the
recently modified curses.rst (how to) file.  Need direction in locating
all of the docs that are impacted by the changes I have introduced and I
will write them up.

I am attaching the diff file for the Docs/library/curses.rst as 
lib_curses_rst.diff

I am attaching the Docs/howto/curses.rst file as howto_curses_rst.diff

I am not familiar with the process here, but I would like to continue 
to add additional support to the _cursesmodule.c file.  However, I am 
loathe to put too much functionality into any one patch.  Is there any 
way I can find out when this patch will be applied so that I can get 
latest and then move forward incrementally?

Thanks for the patches!  Two comments on the addchstr change:

* I think that, instead of checking for a list, the method should accept any Python sequence; a tuple is perfectly reasonable, for example, and if the code is changed to use PyCurses_ConvertToChType() instead of PyInt_Check(), it will accept a list of integers, a mixed list of ints and character strings, and even just strings.

* the documentation and error messages currently try to paper over all of the curses variants of addchstr(), waddchstr(), mvwaddchstr(), ..., covering them all up under the addchstr name.  This means that your submitted documentation patch is too detailed; it should look more like the insnstr() docs, which has [y,x,] as optional, and the text says something like "Moves to y,x if specified, and then ...'.

The color_set() changes look OK; I'm going to try to break them out into a separate patch and commit them on their own.