Util list:
-
ARM, Analysis Module Relationship
通过 import、from-import 分析模块之间的关系.
CodeAnalyzer 还可以一块分析每个模块导的包，所含的类、函数、全局变量
缺陷：
- 只能分析当前文件夹下的所有模块，不递归分析子文件夹（还没写）。
- 仅支持静态分析，分析不了动态的模块导入。
- 分析不了__init__.py中导入的包
- 分析的前提要保障代码的格式规范（以Pycharm的自动代码规范格式为标准）
- CodeAnalyzer只能分析单元素的赋值定义，且赋值的字面值需要缩进不能与赋值定义同缩进.
- CodeAnalyzer暂不支持分析相对导入
-
graph_dot
仅提供了有向图的创建，但重写
__str__()能够输出 dot 格式的图信息。
1 maintainer
Metadata
1 maintainer
Release files for tq-amr 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tq_amr-0.0.1.tar.gz | 11.8 kB | Without provenance | Details for tq_amr-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tq_amr-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for tq_amr-0.0.1-py3-none-any.whl |
Total release size: 24.3 kB
Release files / tq_amr-0.0.1.tar.gz
| Download URL | tq_amr-0.0.1.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36c9c0b90624485134806f9d0b5e93cdbeb651c031f2dccf0ac9eded2bdeb24b
|
|
BLAKE2b-256 checksum How to use checksums |
e46cec93b1ba36afcbc92bb8c0b8fa84c05f264aedb2db69497cc4242ccf3000
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.10
|
Release files / tq_amr-0.0.1-py3-none-any.whl
| Download URL | tq_amr-0.0.1-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1562269adda5be2cdc97ede67f2c8ce741622c70ab97688de9d16e9eb737de52
|
|
BLAKE2b-256 checksum How to use checksums |
a6280be9f9ef44b804299b32888a981f7555977dab525dbcaf0e2f07beb59f6d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.10
|
Security for tq-amr 0.0.1
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.
