From: "Arend van Spriel" <arend@broadcom.com>
To: linux-wireless <linux-wireless@vger.kernel.org>
Subject: interested in py80211?
Date: Wed, 3 Jul 2013 22:57:11 +0200 [thread overview]
Message-ID: <51D49027.9010803@broadcom.com> (raw)
A common say in Linux arena is "when you have an itch, just scratch it".
My itch is that tools like ifconfig and iw are great, but in an
automated test environment it kind of sucks to parse output, which is
confirmed by blurb from iw: "Do NOT screenscrape this tool, we don't
consider its output stable.".
Ever since my first contact with Python I tend to favor it over other
scripting alternatives so I decided to scratch my itch with that and
another old acquaintance called SWIG. With those I went to create
py80211. A first attempt was to have SWIG create a wrapper API directly
exposing the libnl-3 API, but that did not feel comfortable in a
scripting environment. So the level of abstraction is a bit higher. It
is just in a kick-off state (eg. can only send u32 attributes), but I
decided to push it to github anyway.
https://github.com/arend/py80211
Regards,
Arend
next reply other threads:[~2013-07-03 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 20:57 Arend van Spriel [this message]
2013-07-12 8:02 ` interested in py80211? Johannes Berg
2013-07-12 13:32 ` Arend van Spriel
2013-07-24 15:55 ` Will Hawkins
2013-07-24 21:06 ` Arend van Spriel
2013-11-11 8:42 ` Arend van Spriel
2013-11-11 8:54 ` Johannes Berg
2014-01-06 9:30 ` py80211 update on github Arend van Spriel
2014-01-06 10:36 ` Johannes Berg
2014-01-06 10:55 ` Arend van Spriel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51D49027.9010803@broadcom.com \
--to=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).