On Wed, Jun 08, 2016 at 08:55:14AM -0500, Terry Wilson wrote: > The pure Python in-tree JSON parser is *much* slower than the > in-tree C JSON parser. A local test parsing a 100Mb JSON file > showed the Python version taking 270 seconds. With the C wrapper, > it took under 4 seconds. > > The C extension will be used automatically if it can be built. If > the extension fails to build, a warning is displayed and the build > is restarted without the extension. > > The Serializer class is replaced with Python's built-in > JSON library since the ability to process chunked data is not > needed in that case. > > The extension should work with both Python 2.7 and Python 3.3+. > > Signed-off-by: Terry Wilson <twil...@redhat.com>
Applied, thanks! The automatic behavior here is an asset for a developer, but it is probably undesirable for use in packaging systems, because one wants to make sure that the packaging always has or does not have the extension, without depending on what the system has on it. So it might be good to support something like --enable-openssl=[yes|no|check], where "yes" means that OpenSSL must be available, "no" means that OpenSSL will not be used, and "check" (the default) means to use OpenSSL if it's available. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
