Am 06.08.2011 01:02 schrieb Nathan Miller:
After much profiling and a little hair pulling we discovered that version 1.3.1 of TurboJson stopped using simplejson except for versions of python before 2.6. So the new deployment, which had this version, was using the native json library, which is much, much slower.
Hi Nathan, thanks for making us aware of this problem. I naively assumed that there was not such a big difference since the versions included in Python are already the newer ones using the C extension. Therefore using the standard lib module seemed a better idea than using a possibly badly installed simplejson module which e.g. may lack the C speedups if they could not be compiled e.g. under Windows.
But it seems you're right, the performance differences are so huge that the import order should be reversed.
Theoretically we could compare the __version__ of the modules and use the newer one if both are installed, but version comparison is error prone and they are not really comparable anyway - e.g. there were some json improvements in Py 3.2 which are not yet in simplejson.
I can make a TurboJson update this weekend. If there are other issues with TurboJson please let me know so I be fix them in one go.
-- Christoph -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
