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
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
fb1f0dca2a
Make some tuples explicit to pass parsing in py3
2016-06-21 16:27:04 -07:00
70fcc45893
Use print function
2016-06-21 16:27:04 -07:00
79f5d39db5
Comment edits and pass code check
2015-01-17 13:56:37 -08:00
6da3fcdef1
Add bridges s1-s3 to topology and explain some details
2015-01-17 13:38:55 -08:00
7a3159c9af
Spacing tweaks for pep8 checker
2014-12-08 15:10:32 -08:00
4965421215
More pylint fixes...
2014-12-04 02:57:36 -08:00
18aab5b786
More pylint changes
2014-12-04 00:51:05 -08:00
5a530af189
Remove trailing whitespace. ;-/
2014-12-01 15:39:44 -08:00
e0bf8ece3c
Minor code cleanup
2014-11-23 17:17:21 -08:00
2c76ab718b
linuxrouter.py: changing name, printing routing table, and some more documentation
2014-08-27 22:43:04 -07:00
aa4dfda44c
adding documentation and test for linuxrouter.py
2014-08-27 22:01:18 -07:00
8a987b9c55
adding linuxrouter.py
2014-08-27 03:57:38 -07:00
Bob Lantz
Brad Walker
Brian O'Connor