ovs/build-aux/text2c

#! /usr/bin/python3

import re
import sys

"""This utility reads its input, which should be plain text, and
prints it back transformed into quoted strings that may be #included
into C source code."""

while True:
    line = sys.stdin.readline()
    if not line:
        break

    s = line.replace("\\", "\\\\").replace('"', '\\"').replace("\n", "\\n")
    print('"' + s + '"')
Require Python 3 and remove support for Python 2. Python 2 reaches end-of-life on January 1, 2020, which is only a few months away. This means that OVS needs to stop depending on in the next release that should occur roughly that same time. Therefore, this commit removes all support for Python 2. It also makes Python 3 a mandatory build dependency. Some of the interesting consequences: - HAVE_PYTHON, HAVE_PYTHON2, and HAVE_PYTHON3 conditionals have been removed, since we now know that Python3 is available. - $PYTHON and $PYTHON2 are removed, and $PYTHON3 is always available. - Many tests for Python 2 support have been removed, and the ones that depended on Python 3 now run unconditionally. This allowed several macros in the testsuite to be removed, making the code clearer. This does make some of the changes to the testsuite files large due to indentation level changes. - #! lines for Python now use /usr/bin/python3 instead of /usr/bin/python. - Packaging depends on Python 3 packages. Acked-by: Numan Siddique <nusiddiq@redhat.com> Tested-by: Numan Siddique <nusiddiq@redhat.com> Signed-off-by: Ben Pfaff <blp@ovn.org> 2019-09-20 08:30:42 -07:00			`#! /usr/bin/python3`
ovsdb-server: Add support for a built-in _Server database. The _Server database is valuable primarily because it provides database clients a way to find out the details of changes to databases, schemas, etc. in a granular, natural way. Until now, the only way that the server could notify clients about these kinds of changes was to close the session; when the client reconnects, it is expected to reassess the server's state. One way to provide this kind of granular information would be to add specific JSON-RPC requests to obtain notifications for different kinds of changes, but since ovsdb-server already provides granular and flexible notification support for databases, using a database for the purpose is convenient and avoids duplicating functionality. Initially this database only reports databases' names and schemas, but when clustering support is added in a later commit it will also report important aspects of clustering and cluster status. Thus, this database also reduces the need to add JSON-RPC calls to retrieve information about new features. Signed-off-by: Ben Pfaff <blp@ovn.org> 2017-12-15 11:14:55 -08:00
			`import re`
			`import sys`

			`"""This utility reads its input, which should be plain text, and`
			`prints it back transformed into quoted strings that may be #included`
			`into C source code."""`

			`while True:`
			`line = sys.stdin.readline()`
			`if not line:`
			`break`

			`s = line.replace("\\", "\\\\").replace('"', '\\"').replace("\n", "\\n")`
			`print('"' + s + '"')`