delta/openvswitch.git - github.com: openvswitch/ovs.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	python: Remove unused imports.	Ben Pfaff	2011-08-25	1	-1/+0
\| \| \| \|	Found by pychecker.
*	ovs.stream: Remove unused parameter from usage().	Ben Pfaff	2011-08-25	1	-1/+1
\| \| \| \|	This function has no callers. We could delete it entirely, instead.
*	ovs.stream: Simplify logic in Stream.wait().	Ben Pfaff	2011-08-24	1	-3/+3
\| \| \| \|	Suggested-by: Reid Price <reid@nicira.com>
*	ovs.stream: Drop Stream.get_name() since clients can use 'name' directly.	Ben Pfaff	2011-08-24	1	-3/+0
\| \| \| \|	Suggested-by: Reid Price <reid@nicira.com>
*	ovs.stream: Use %d in place of %ld since the two are equivalent in Python.	Ben Pfaff	2011-08-24	1	-3/+3
\| \| \| \|	Reported-by: Reid Price <reid@nicira.com>
*	python: Avoid using 'tuple' as a variable name.	Ben Pfaff	2011-08-24	1	-4/+3
\| \| \| \| \| \| \|	'tuple' is a Python built-in function, so it's best to avoid using it as a variable name. Suggested-by: Reid Price <reid@nicira.com>
*	ovs.stream: Fix logic bug in Stream.connect().	Ben Pfaff	2011-08-24	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \|	The loop here is supposed to run at least once, and to continue looping as long as the loop body changes the current state, but this bug caused it to continue looping until the connection completed in success or failure. It probably didn't cause many problems in practice because only Unix domain socket connections are currently supported, and those connections normally complete immediately. Reported-by: Reid Price <reid@nicira.com>
*	Implement initial Python bindings for Open vSwitch database.	Ben Pfaff	2010-08-25	1	-0/+316
	These initial bindings pass a few hundred of the corresponding tests for C implementations of various bits of the Open vSwitch library API. The poorest part of them is actually the Python IDL interface in ovs.db.idl, which has not received enough attention yet. It appears to work, but it doesn't yet support writes (transactions) and it is difficult to use. I hope to improve it as it becomes clear what semantics Python applications actually want from an IDL.