[qmtest] Patch 2.0.3 or use latest CVS?

Mark Mitchell mark at codesourcery.com
Fri Jan 2 21:51:36 UTC 2004


>  File "/opt/nextest/lib/qm/qm/test/qmtest.py", line 78, in ?
>     exit_code = command.Execute()
>   File "/lib/qm/qm/test/cmdline.py", line 569, in Execute
>   File "/lib/qm/qm/test/cmdline.py", line 1099, in __ExecuteRemote
>   File "/opt/nextest/lib/python2.3/copy_reg.py", line 50, in
> _reconstructor
>     obj = base.__new__(cls, state)
> TypeError: ('dict.__new__(X): X is not a type object (classobj)',
> <function _reconstructor at 0x81827d4>, (<class
> qm.test.context.Context at 0x833477c>, <type 'dict'>, {}))

That's a very strange error and backtrace.

What operating system are you running on?

> Should I go with 2.0.3 for production use and apply the patches?  
> Are there any glaring deficiencies in 2.0.3?  

I would currently recommend the CVS version, simply because 2.0.3 has
gotten fairly out of date at this point.  The CVS version should be
quite stable, despite your experience above.

> On a related note, should I send documentation errors and bugs to this
> list?

Yes, this is the right list for documentation errors and bugs.

Thanks,

-- 
Mark Mitchell <mark at codesourcery.com>
CodeSourcery, LLC




More information about the qmtest mailing list