[Bf-python] Cutting down PyArg_ParseTuple() exception verbage and other cruft

[Stephen Swaney]

On Thu, Jun 01, 2006 at 12:36:21PM -0700, Ken Hughes wrote:

>   [snip] 
> Since our original message isn't giving any more real information, how 
> about we just use the internal exceptions in these simple cases?
>  [snip] 

Less code is generally better, from both a maintenance and debuging
perspective.  Readable code is good code.

I will note that it was often easy to zoom in on a bug
due to the unique error msg.  Especially if it was mispelled or written
in quaint Europenglish.

Just thinking out loud, I wonder if it is worthwhile to have a 
couple of #defines for NULL and -1 to keep PyObj error and
PyInt error return values straight?  Or maybe just a Post-It 
on the monitor?

Bottom line, cleanup is OK by me.

-- 
Stephen Swaney			
sswaney at centurytel.net