Python Module: a2y_kcom
a2y_kcom 实现内核科技 USB（HID）转多通道UART 的驱动程序。从原先的 hidcom 模块更名而来，从 2024 年 6 月 15 日起，正式把串口名更改为 KCOM。 原先的名字“HidCom”还将延续一段时间，以保持兼容性。
ChangeLog
-
2026-11-01 增加“数据位”、“校验位”和“停止位”的配置功能。升级版本号为 ０.9.0。
-
2025-05-02 增加接口
reset_input_buffer，逐步修正之前对flush相关函数的误解。升级版本号为 0.8.4。 -
2024-09-17 Fix bug in function
read_until. Release version 0.8.3 -
2024-08-24 Fix bug. Release version 0.8.2
-
2024-08-09 升级版本号为 0.8.1。
- 加入接口
list_kcom_names，以方便获取当前系统存在的所有KCOM串口通道名。 但当前的实现有缺陷：仅仅是列出串口通道名，将导致进程打开并占用整个KCOM设备，以至所有的KCOM通道将只能由此进程打开使用。 - 给
Serial构造函数加入**kwargs参数，以解决有多余参数造成不能打开串口通道的问题。
- 加入接口
-
2024-06-15 创建模块，发布版本 0.8.0
1 maintainer
Metadata
1 maintainer
Release files for a2y-kcom 0.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| a2y_kcom-0.9.0-cp312-cp312-win_amd64.whl | CPython 3.12 | CPython 3.12 | Windows x86-64 | Details for a2y_kcom-0.9.0-cp312-cp312-win_amd64.whl |
Release files / a2y_kcom-0.9.0-cp312-cp312-win_amd64.whl
| Download URL | a2y_kcom-0.9.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 139.5 kB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7739deb5dd4924e38f91f19133253fda10848513f4d8796c7234672d79285caa
|
|
BLAKE2b-256 checksum How to use checksums |
30163d4e1b18ee1a10706cb08ccff4062019c0f4834987bb42d2304ec58af887
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
Security for a2y-kcom 0.9.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
