summaryrefslogtreecommitdiffstats
path: root/python/examples
Commit message (Collapse)AuthorAgeFilesLines
* python: fix flake8 warnings F841Thomas Haller2023-07-252-4/+4
| | | | | | | | | ./python/examples/iface.py:66:5: F841 local variable 'e' is assigned to but never used ./python/examples/iface.py:66:5: F841 local variable 'e' is assigned to but never used ./python/examples/iface.py:109:1: F841 local variable 'e' is assigned to but never used ./python/examples/wiphy.py:116:5: F841 local variable 'e' is assigned to but never used ./python/examples/wiphy.py:116:5: F841 local variable 'e' is assigned to but never used ./python/examples/wiphy.py:158:1: F841 local variable 'e' is assigned to but never used
* python: reformat all Python files with python-blackThomas Haller2023-07-253-890/+925
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automated code formatting is great. Use python-black for that ([1]). Black us not configurable much (uncompromising) and follows PEP8. It thus generates quite a standard, pleasing format. But the point isn't whether the formatting is always the most subjectively pleasing. The point is that the style is generated and enforceable by an automated tool. It takes away places for nit picking, while resulting in a more consistent code base. As this reformats the entire code base, it introduces a large diff and interferes with tools like git-blame. That will be somewhat alleviated by adding a "blame.ignoreRevsFile" for git in the next commit. The change is done automatically, by running python-black version black-22.8.0-2.fc38.noarch: $ black . The result is the same as $ ( git grep -l '#!.*\(PYTHON\|python\)' ; git ls-files '*.py' '*.py.in' ) \ | sort -u \ | xargs -d '\n' black Note that the exact result depends on the version of black. Currently that version is black==22.12.0 from pip. Yes, this means when we bump the version in the future, some reformatting will happen. [1] https://github.com/psf/black
* Use print() function in both Python 2 and Python 3Christian Clauss2022-07-062-29/+31
| | | | https://github.com/thom311/libnl/pull/327
* build: merge python/Makefile.am into top-level makefileThomas Haller2017-02-271-6/+0
|
* python: Include all files in distributionThomas Graf2013-11-061-0/+6
| | | | Signed-off-by: Thomas Graf <tgraf@suug.ch>
* python: remove use of PyArg_ParseTuple() for callback resultArend van Spriel2013-10-071-1/+1
| | | | | | | | | | | | | | The message receive callback handler in the netlink api processes the result object from the python callback. It used PyArg_ParseTuple() to get the value, but this does not work as intended (see ref [1]). Instead check the type and convert it accordingly. refs: [1] http://stackoverflow.com/questions/13636711/what-is-the-proper-usage-of-pyarg-parsetuple Reported-by: Teto <mattator@gmail.com> Signed-off-by: Arend van Spriel <arend@broadcom.com> Signed-off-by: Thomas Graf <tgraf@suug.ch>
* add python examples using swig provided apiArend van Spriel2013-09-053-0/+1811
using the nl80211 family to show use of generic netlink api and attribute parsing. Signed-off-by: Arend van Spriel <arend@broadcom.com> Signed-off-by: Thomas Graf <tgraf@suug.ch>
generated by cgit v0.12 at 2025-08-26 03:08:25 (GMT)