7 Commits

Author	SHA1	Message	Date
Bob Lantz	ee15ce2243	print -> info; end the horror of print vs. print() ... Although we could use print() from __future__, this messes up scripts which use examples as modules. The simple, if not nicest for 2.7, solution is to use info(), output() and other mininet.log functions. The disadvantage is that we may have to adjust things if we change info() to add automatic newlines, but we can burn that bridge in Mininet 3.x.	2016-08-23 01:54:54 -07:00
Bob Lantz	8ac077a721	Remove "from __future__ import print" ... This was well-intentioned, but it causes more trouble than it's worth. Fixes #652	2016-08-08 15:28:52 -07:00
Brad Walker	fb1f0dca2a	Make some tuples explicit to pass parsing in py3	2016-06-21 16:27:04 -07:00
Brad Walker	70fcc45893	Use print function	2016-06-21 16:27:04 -07:00
Bob Lantz	0fe73a6780	build=False is unnecessary if topo=None, which is the default	2014-03-16 05:20:43 -07:00
Bob Lantz	dcb3036b70	Change to use addLink() interface for symmetry/consistency.	2013-03-06 16:55:47 -08:00
Bob Lantz	31e1ff7154	Rename controllers.py to controllers2.py since it's less convenient.	2013-02-28 17:55:41 -08:00