CANConfigPython 0.1.0a1__py3-none-win_amd64.whl → 0.1.0a2__py3-none-win_amd64.whl

canconfigpython/__init__.py

@@ -1,7 +1,7 @@
-"""CANConfigPython: subprocess-isolated CAN device configuration."""
-__version__ = "0.1.0a1"
-
-from .client import Client
-from .errors import ConfigError
-
-__all__ = ["Client", "ConfigError", "__version__"]
+"""CANConfigPython: subprocess-isolated CAN device configuration."""
+__version__ = "0.1.0a2"
+
+from .client import Client
+from .errors import ConfigError
+
+__all__ = ["Client", "ConfigError", "__version__"]

canconfigpython/resources/docs/user-guide.en.md

@@ -1,31 +1,35 @@
 # CANConfigPython user guide
 
-Applies to Python CLI 0.1.0a1 / Console 2.3 / bridge API 1.
+Applies to Python CLI 0.1.0a2 / Console 2.3 / bridge API 1.
 Supports configuration of CANHub, CANFB, CANBridge, CANRPT and CANCOM.
 Consult the release validation record for tested platforms and hardware evidence.
 
 ## Install and check without hardware
 
-Use Python 3.8+ in a virtual environment. Install the supplied wheel matching your
-platform; until publication there is no public package to install.
+Use Python 3.8+ in a virtual environment. Install this release from PyPI; pip
+selects the wheel matching your platform.
 The wheel includes Console, WIICAN and required Qt libraries. No GUI installation
-or graphical desktop is needed.
+or graphical desktop is needed. Windows win32 includes 32-bit native files;
+win_amd64 includes 64-bit native files. pip selects by Python architecture.
+This release uses Qt 5.15.2. In `doctor --json`, `data.qt_version` reports the
+loaded Qt and `data.runtime_manifest.architecture` reports the native architecture.
 
 Windows PowerShell:
 ~~~powershell
 python -m venv .venv
-.\.venv\Scripts\python.exe -m pip install .\canconfigpython-0.1.0a1-py3-none-win_amd64.whl
+.\.venv\Scripts\python.exe -m pip install CANConfigPython==0.1.0a2
 .\.venv\Scripts\canconfig.exe doctor --json
 ~~~
 
 Linux: create an environment with `python3 -m venv .venv`, activate with
-`. .venv/bin/activate`, then install the actual supplied Linux wheel using
-`python -m pip install ./WHEEL_FILENAME.whl`. Its manylinux tag states the minimum
-glibc version established by the build. This release requires x86_64 and glibc 2.38+;
-it was built/tested on Ubuntu 24.04 / Python 3.12 with Qt 5.15.13.
+`. .venv/bin/activate`, then install with
+`python -m pip install CANConfigPython==0.1.0a2`. Its manylinux tag states the minimum
+glibc version established by the build: this x86_64 wheel requires glibc 2.38
+or newer, with installation tested on Ubuntu 24.04.
 Use `ldd --version` to check glibc. ARM64, musl and macOS are not supported.
 
-After publication: `python -m pip install --pre CANConfigPython`.
+To install a downloaded wheel, use `python -m pip install ./WHEEL_FILENAME.whl`
+with the actual filename for your platform.
 Upgrade: `python -m pip install --upgrade --pre CANConfigPython`.
 Uninstall: `python -m pip uninstall CANConfigPython`. Your backups and exported
 documentation/Skill remain your files.
@@ -272,3 +276,8 @@ Ymodem implementation; Qt and compiler libraries retain their own licenses.
 `canconfig docs export --output ./canconfig-docs` also exports `native-source.tar.gz`.
 Extract it and follow DEVELOPING.md to rebuild the native programs. See its
 THIRD_PARTY_NOTICES.md for license materials and dependency source locations.
+
+The Linux Qt 5.15.2 runtime includes upstream fixes for current GCC. After
+`canconfig docs export --output NEW_DIRECTORY`, `qt5152-linux-source.tar.xz`
+contains the full Qt source, patch and build record; `native-source.tar.gz`
+contains the Console/WIICAN and Python project source. Export opens no device.

canconfigpython/resources/docs/user-guide.zh-CN.md

@@ -1,32 +1,36 @@
 # CANConfigPython 用户操作说明
 
-适用版本：Python CLI 0.1.0a1 / Console 2.3 / bridge API 1。
+适用版本：Python CLI 0.1.0a2 / Console 2.3 / bridge API 1。
 Windows 和 Linux 使用相同命令。Linux 包的实测状态以发布包附带的验证记录为准。
 本工具面向 CANHub、CANFB、CANBridge、CANRPT、CANCOM 配置，不提供 CAN 报文发送功能。
 
 ## 1. 安装与第一次成功运行
 
-在保存发布文件的目录打开 PowerShell 或 Linux 终端。需要 Python 3.8 或以上。
+打开 PowerShell 或 Linux 终端。需要 Python 3.8 或以上。
 建议创建虚拟环境；运行时无需单独安装 Qt、WIICAN 或 GUI。
+Windows 的 win32 包内为 32 位 Console/DLL，win_amd64 包内为 64 位；pip 按 Python 位数选择。
+本版使用 Qt 5.15.2。`doctor --json` 的 `data.qt_version` 显示实际加载版本，
+`data.runtime_manifest.architecture` 显示原生程序架构。
 
-Windows PowerShell（按实际 wheel 文件名替换）：
+Windows PowerShell（从 PyPI 安装）：
 ~~~powershell
 python -m venv .venv
-.\.venv\Scripts\python.exe -m pip install .\canconfigpython-0.1.0a1-py3-none-win_amd64.whl
+.\.venv\Scripts\python.exe -m pip install CANConfigPython==0.1.0a2
 .\.venv\Scripts\canconfig.exe doctor --json
 ~~~
 
-Linux x86_64（需要 glibc 2.38 或以上，已在 Ubuntu 24.04 / Python 3.12 上验证）：
+Linux x86_64（glibc 2.38 或以上）：
 ~~~bash
 python3 -m venv .venv
 . .venv/bin/activate
-python -m pip install ./canconfigpython-0.1.0a1-py3-none-manylinux_2_38_x86_64.manylinux_2_39_x86_64.whl
+python -m pip install CANConfigPython==0.1.0a2
 canconfig doctor --json
 ~~~
 
-可用 `ldd --version` 查看 glibc 版本。当前 Linux 包不适用于低于 2.38 的 glibc、ARM64 或 musl 系统。
+可用 `ldd --version` 查看 glibc 版本；最低要求以 wheel 的 manylinux 标签为准。
+本版最低要求为 glibc 2.38，已在 Ubuntu 24.04 验证安装。ARM64 和 musl 不受支持。
 安装成功后可激活环境，或使用其完整可执行文件路径。后续以 canconfig 简写。
-已上传 PyPI 后才可以使用 `python -m pip install --pre CANConfigPython`。
+也可安装已下载的匹配平台 wheel：`python -m pip install ./WHEEL_FILENAME.whl`，将占位名称替换为实际文件名。
 升级用 `python -m pip install --upgrade --pre CANConfigPython`；
 卸载用 `python -m pip uninstall CANConfigPython`。备份和已导出的说明/Skill 不会被卸载删除。
 
@@ -263,3 +267,7 @@ Python 包装层采用 MIT。随包 Console 包含 XinLi 的 GPLv3-or-later Ymod
 `canconfig docs export --output ./canconfig-docs` 会一起导出
 `native-source.tar.gz`。解压后按其中的 DEVELOPING.md 重建原生程序，
 THIRD_PARTY_NOTICES.md 列出了许可和外部依赖的源码位置。
+
+Linux 版随包 Qt 5.15.2 包含适配新 GCC 的上游修复。执行 `canconfig docs export --output NEW_DIRECTORY`
+后，`qt5152-linux-source.tar.xz` 包含完整 Qt 对应源码、补丁和构建记录；
+`native-source.tar.gz` 包含 Console/WIICAN 与 Python 项目源码。导出无需连接设备。

canconfigpython/resources/skill/canconfig-python/SKILL.md

@@ -1,71 +1,71 @@
----
-name: canconfig-python
-description: Use CANConfigPython on Windows or Linux to inspect CAN device identity, export or restore INI backups, apply JSON configuration, change passwords, or update firmware on an explicit serial port. Use for CLI operations and troubleshooting, not CAN traffic generation or firmware development.
----
-
-# CANConfigPython device operations
-
-Read [the operation reference](references/operations.md) for the selected task.
-For parameter edits, select a device-specific request from
-[the example catalog](assets/examples/index.en.md) or
-[中文用例目录](assets/examples/index.zh-CN.md), using
-[changes.schema.json](assets/changes.schema.json) for offline structure checks.
-
-## Identify and prepare
-
-1. Run `canconfig --version --json` and `canconfig doctor --json`. This Skill targets
-   Python 0.1.0a1, Console 2.3, bridge API 1. Doctor opens no device.
-2. Use the user-selected explicit COM port on Windows or /dev path on Linux.
-   Query info when authorized to connect. It returns identity, capabilities and field
-   names, not a complete current configuration. Info/configuration dry-run can
-   change device run mode.
-3. Match UID, model and capabilities to the task. Ask only for missing target/scope;
-   existing authorization remains valid. Prepare a concrete reviewable request
-   before any additional approval that is actually required.
-4. Copy a suitable example. Only replace its all-zero placeholder UID using the
-   confirmed target. A mismatch in an existing request/backup is a stop condition,
-   not permission to rewrite it. Change only authorized fields. A partial patch may
-   write an entire section and associated SAVE domains.
-
-## Execute and interpret
-
-- Use UTF-8 JSON without BOM containing exactly schema_version, device_uid and
-  changes. Python rejects duplicate keys and nonfinite numbers. Stop on preparation
-  errors; do not accidentally apply a previous file. Schema/results are envelopes,
-  not patch files. Validate accepts INI backups only.
-- Pass credentials through short-lived environment variables (--password-env);
-  the API accepts in-memory passwords. Never pass secrets in argv, logs, committed
-  files, reports or chat. Clear caller variables in finally/trap paths covering
-  preparation, invocation and result parsing.
-- For configuration writes, run the matching live dry-run, inspect its scope, then
-  execute the unchanged request within existing authorization. A dry-run is not a
-  reservation; execution repeats preflight.
-- Check process exit, ok, effects and verification. On partial/unknown effects,
-  timeout, cancellation, mismatch or missing final JSON, stop automatic retry and
-  rollback; report known effects and uncertainty. Missing output means counts can
-  be null, not zero. Do not infer power-cycle persistence.
-
-## Device-specific boundaries
-
-- Adaptive enable must be a separate patch containing only selected
-  CANn_PARAMETER/BRT_AUTO: 1 fields. All channels must initially have unrestricted
-  manual parameters. It verifies flags only, not detected baud rate.
-- Never export/write back adaptive detected timings/placeholders for any role.
-  Do not disable adaptive merely to get a backup. Returning to manual requires
-  explicitly authorized new manual parameters for every channel.
-- Same-device restore uses --expect-uid and --check-device. Cross-device migration
-  requires explicit scope; retain target --expect-uid, omit --check-device only for
-  that authorized migration.
-- Password change requires explicit UID and distinct old/new environment names.
-  Dry-run authenticates the old password without changing it. Success confirms one
-  new-password authentication, not persistence after power cycle.
-- Firmware .sfb dry-run is offline. Pin SHA-256, confirm external model/image
-  compatibility and that the selected device is already in update mode. Do not add
-  configuration UID/password flags. Transmission plus port return does not prove
-  installed version, signature, compatibility or power-cycle behavior.
-
-## Report
-
-State target, scope, actual effects/verification and needed next action.
-Distinguish simulated/offline checks from physical-device validation.
-Do not disclose passwords or adaptive detected timings.
+---
+name: canconfig-python
+description: Use CANConfigPython on Windows or Linux to inspect CAN device identity, export or restore INI backups, apply JSON configuration, change passwords, or update firmware on an explicit serial port. Use for CLI operations and troubleshooting, not CAN traffic generation or firmware development.
+---
+
+# CANConfigPython device operations
+
+Read [the operation reference](references/operations.md) for the selected task.
+For parameter edits, select a device-specific request from
+[the example catalog](assets/examples/index.en.md) or
+[中文用例目录](assets/examples/index.zh-CN.md), using
+[changes.schema.json](assets/changes.schema.json) for offline structure checks.
+
+## Identify and prepare
+
+1. Run `canconfig --version --json` and `canconfig doctor --json`. This Skill targets
+   Python 0.1.0a2, Console 2.3, bridge API 1. Doctor opens no device.
+2. Use the user-selected explicit COM port on Windows or /dev path on Linux.
+   Query info when authorized to connect. It returns identity, capabilities and field
+   names, not a complete current configuration. Info/configuration dry-run can
+   change device run mode.
+3. Match UID, model and capabilities to the task. Ask only for missing target/scope;
+   existing authorization remains valid. Prepare a concrete reviewable request
+   before any additional approval that is actually required.
+4. Copy a suitable example. Only replace its all-zero placeholder UID using the
+   confirmed target. A mismatch in an existing request/backup is a stop condition,
+   not permission to rewrite it. Change only authorized fields. A partial patch may
+   write an entire section and associated SAVE domains.
+
+## Execute and interpret
+
+- Use UTF-8 JSON without BOM containing exactly schema_version, device_uid and
+  changes. Python rejects duplicate keys and nonfinite numbers. Stop on preparation
+  errors; do not accidentally apply a previous file. Schema/results are envelopes,
+  not patch files. Validate accepts INI backups only.
+- Pass credentials through short-lived environment variables (--password-env);
+  the API accepts in-memory passwords. Never pass secrets in argv, logs, committed
+  files, reports or chat. Clear caller variables in finally/trap paths covering
+  preparation, invocation and result parsing.
+- For configuration writes, run the matching live dry-run, inspect its scope, then
+  execute the unchanged request within existing authorization. A dry-run is not a
+  reservation; execution repeats preflight.
+- Check process exit, ok, effects and verification. On partial/unknown effects,
+  timeout, cancellation, mismatch or missing final JSON, stop automatic retry and
+  rollback; report known effects and uncertainty. Missing output means counts can
+  be null, not zero. Do not infer power-cycle persistence.
+
+## Device-specific boundaries
+
+- Adaptive enable must be a separate patch containing only selected
+  CANn_PARAMETER/BRT_AUTO: 1 fields. All channels must initially have unrestricted
+  manual parameters. It verifies flags only, not detected baud rate.
+- Never export/write back adaptive detected timings/placeholders for any role.
+  Do not disable adaptive merely to get a backup. Returning to manual requires
+  explicitly authorized new manual parameters for every channel.
+- Same-device restore uses --expect-uid and --check-device. Cross-device migration
+  requires explicit scope; retain target --expect-uid, omit --check-device only for
+  that authorized migration.
+- Password change requires explicit UID and distinct old/new environment names.
+  Dry-run authenticates the old password without changing it. Success confirms one
+  new-password authentication, not persistence after power cycle.
+- Firmware .sfb dry-run is offline. Pin SHA-256, confirm external model/image
+  compatibility and that the selected device is already in update mode. Do not add
+  configuration UID/password flags. Transmission plus port return does not prove
+  installed version, signature, compatibility or power-cycle behavior.
+
+## Report
+
+State target, scope, actual effects/verification and needed next action.
+Distinguish simulated/offline checks from physical-device validation.
+Do not disclose passwords or adaptive detected timings.

canconfigpython/runtime/manifest.json

@@ -1,19 +1,20 @@
 {
   "format": 1,
   "platform": "windows",
-  "architecture": "x86",
-  "wheel_platform": "win32",
+  "architecture": "x86_64",
+  "wheel_platform": "win_amd64",
+  "qt_version": "5.15.2",
   "backend_version": "2.3",
   "bridge_api": 1,
   "executable": "canconfigconsole.exe",
   "sha256": {
-    "Qt5Core.dll": "0a4da23fbfdab54c975bff15717137acd8738c19dc8a4a9aa3f5c7b9a7d94585",
-    "Qt5Network.dll": "02a0b66118b459113e4c060d3a49210ca6e53a6bc7f9ad8561b22f71bbbff0c3",
-    "Qt5SerialPort.dll": "7158896af1688d100fc4a231712b92ac03248acd65c030ec9617b8f3fd79e6b8",
-    "WIICAN.dll": "1e8a69aa368db34cf701bbfca0b616459430f4e17606279c7b9477841dd83268",
-    "canconfigconsole.exe": "504f0df4da6a46d5c679f67698678e9b32f0ab3ef2ab9e6df7d250790fe91a07",
-    "libgcc_s_dw2-1.dll": "4d2e2d408d399d066b0aaef2047f7a33515c13c589832de0d9f1ba87a530c394",
-    "libstdc++-6.dll": "79622396dc4c7afbbceca03e69f727bf1862735ee3ad671aa3ee7ada8aa446c3",
-    "libwinpthread-1.dll": "b5fe4d6408ef2baabdd168f4c7250900606468e9aeb24c71e0c833d3d715ae65"
+    "Qt5Core.dll": "858abb9ddcb3cd4fa15c01d3cd64ff4371a79516b02bc3df20590a82161fba55",
+    "Qt5Network.dll": "7660849b5647d0cd1c893fd0f977474df7b968bfae17cec79dbc77359f4e01f3",
+    "Qt5SerialPort.dll": "9aac00c9af50e353b6aa4b67ccc6651fe326bcd47646070750bd2d491ccc9319",
+    "WIICAN.dll": "adf7026f7485ecef3e9de28c55ccec687d0cfc453fb6eda25630f66d7bdf0a6c",
+    "libgcc_s_seh-1.dll": "438ae82ffd621a2413199155574cc85681f8986f05420b1485aa4be936c3bc0b",
+    "libstdc++-6.dll": "72ce15df7c50e8d0ca57701b0b37394942e5348654505fcb993873b515dfd1d0",
+    "libwinpthread-1.dll": "5bbef249a0d00e2d32c699d0bbe89f714ebeb872b3990a5cbeccb1d89f63e5e8",
+    "canconfigconsole.exe": "00bb418dcd2102debdd552647dc9748d176db238feb3ef9a73a5d8a69771c5f5"
   }
 }