[pox-dev] CLI with POX
Murphy McCauley
murphy.mccauley at gmail.com
Wed Oct 3 03:05:18 PDT 2012
On Oct 3, 2012, at 2:41 AM, William Emmanuel Yu wrote:
> As of betta, running pox.py will no longer drop me into a CLI. I would
> like to go back to the old behavior. How do I do this? I tried
> spelunking the code myself but it wasn't very obvious.
Yeah; I'm not sure where to document this. Maybe add something in the readme. Certainly update the wiki, though I am loathe to update the wiki with things that are betta-specific yet.
The "py" component now provides the CLI, so just stick "py" on your commandline.
> Btw, there is a bug with respect to passing parameters to pox.py. Here
> is a small patch to fix it:
Are you sure this is necessary? Some things to note which might be causing confusion:
boot() trims the first entry off of sys.argv[].
boot() manipulates argv -- it's prepends "py --disable" to the commandline to ensure that py loads early (of_01 will probably work similarly at some point, it's currently special-cased to load early).
> For some reason, using the passed variable argv refers to all the system
> arguments and not the parameter passed to the function. Strange.
This definitely doesn't seem to be the case on my system. Could it be one of the above-mentioned complications? What does "print argv" around like 126 in boot.py show?
-- Murphy
More information about the pox-dev
mailing list