Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| bc3144e9 | 2026-09-11 08:40:20 | update to py3-command_runner-1.7.6 | ||
| b34b1b46 | 2025-11-14 15:36:42 | Update to py3-command_runner-1.7.5. | ||
| 85d40ef7 | 2025-07-17 14:14:46 | update to py3-command_runner-1.7.4 | ||
| 8d45c98e | 2025-04-29 10:40:01 | sync PLISTs for setuptools ports | ||
| 37b3a9f2 | 2024-12-21 11:38:51 | handle py3.12 switchover in sysutils | ||
| 384eb285 | 2024-05-06 12:23:55 | bump REVISION for py3.10 -> py3.11 switch | ||
| 1427b990 | 2022-11-13 15:29:41 | bump for MODPY_DEFAULT_VERSION_3 change | ||
| 2206a800 | 2022-09-13 20:56:17 | rename MODPY_PEP517 to MODPY_PYBUILD which is a bit less of a magic-numbers name and more of a nod at the frontend we're actually using for the build. | ||
| fa37916d | 2022-08-21 13:26:24 | import /usr/ports/mystuff/sysutils/py-command_runner, ok kmos@ command_runner's purpose is to run external commands from Python, just like "subprocess" on which it relies, while solving various problems a developer may face, including: - Handling of all possible subprocess.popen / subprocess.check_output scenarios / python versions in one handy function without encoding / timeout hassle. - Allow stdout/stderr stream output to be redirected to callback functions / output queues / files so you get to handle output in your application while commands are running. - Callback to optional stop check so we can stop execution from outside command_runner. - Callback with optional process information so we get to control the process from outside command_runner. |