[Xapian-tickets] [Xapian] #297: Python bindings `xapian.cvar` raises strange NameError in unexpected circumstances

[Xapian]

#297: Python bindings `xapian.cvar` raises strange NameError in unexpected
circumstances
---------------------+------------------------------------------------------
 Reporter:  exarkun  |       Owner:  richard  
     Type:  defect   |      Status:  new      
 Priority:  low      |   Milestone:  1.1.4    
Component:  Other    |     Version:  SVN trunk
 Severity:  normal   |    Keywords:           
Blockedby:           |    Platform:  All      
 Blocking:           |  
---------------------+------------------------------------------------------
Changes (by olly):

  * priority:  normal => low


Comment:

 It seems BAD_VALUENO comes from xapian.cvar from adding printf tracing to
 where we scan, but nothing else seems to and we can probably persuade that
 to be provided as other constants are.

 And it's trying to read __bases__ when it fails.  If I add code to return
 Py_NONE for that, then I get:

 {{{
 TypeError: issubclass() arg 1 must be a class
 }}}

 Is that better?  I really don't know this stuff well enough to know, but
 if it is we can probably make that change in SWIG.

 But perhaps it would be better to persuade BAD_VALUENO not to be in cvar,
 and then (if it doesn't already) get SWIG to just suppress cvar if it
 would be empty.

-- 
Ticket URL: <http://trac.xapian.org/ticket/297#comment:4>
Xapian <http://xapian.org/>
Xapian