pyrcl
Release Notes
v1.1.6
- Fixed handling of
SNANand-SNAN - Fixed
library.t32_notifystateenable
v1.1.5
- Fixed
Breakpointstring representation to include missingsizeandcorefields - Fixed
library.t32_readtraceencoding issue - Added new functions
library.t32_gettracestate64andlibrary.t32_readtrace64for larger trace sizes
v1.1.4
- Marked
MemoryErroras deprecated, useMemoryAccessErrorinstead - Marked
MemoryReadErroras deprecated, useMemoryReadAccessErrorinstead - Marked
MemoryWriteErroras deprecated, useMemoryWriteAccessErrorinstead
v1.1.3
- Added support for readthedocs
v1.1.2
- Fixed an issue where a TCP connection closed by the peer was not properly detected
v1.1.1
- Fixed memory bundles
v1.1.0
- Drop support for Python 3.6, 3.7, 3.8
- Add support for memory bundles
- Add partial support for direct access API
v1.0.10
- Added missing functions
library.t32_gettracestateandlibrary.t32_readtrace - Changed logger name to "lauterbach.trace32.rcl"
v1.0.9
- Fixed error related functions to not use dbg.fnc(), otherwise the error state is reset. Affected functions:
- def error_address(self) -> Address: (dropped)
- def error_cmdline(self) -> str:
- def error_fileline(self) -> int: (dropped)
- def error_filename(self) -> str: (dropped)
- def error_firstid(self) -> str:
- def error_id(self) -> str:
- def error_message(self) -> str:
- def error_occurred(self) -> bool:
- def error_position(self) -> int: (dropped)
v1.0.8
- Fixed missing breakpoint actions
WATCH,TRACEENABLE,TRACEDATA,TRACEON,TRACEOFFandTRACETRIGGER
v1.0.7
- Fixed missing module level export of
hexversion()
v1.0.6
- Fixed missing module level exports of
versionand multiple exceptions - Fixed breakpoint core and size parameters
- Added
ConnectionErroras baseclass ofApiConnectionError
v1.0.5
Various bugfixes
v1.0.4
Various bugfixes
v1.0.3
Various bugfixes
v1.0.2
Various bugfixes
v1.0.1
Various bugfixes
v1.0.0
Initial release
Metadata
Release files for lauterbach-trace32-rcl 1.1.6
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 |
|---|---|---|---|---|
| lauterbach_trace32_rcl-1.1.6.tar.gz | 88.6 kB | Without provenance | Details for lauterbach_trace32_rcl-1.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lauterbach_trace32_rcl-1.1.6-py3-none-any.whl | Python 3 | none | any | Details for lauterbach_trace32_rcl-1.1.6-py3-none-any.whl |
Total release size: 173.0 kB
Release files / lauterbach_trace32_rcl-1.1.6.tar.gz
| Download URL | lauterbach_trace32_rcl-1.1.6.tar.gz |
|---|---|
| Size | 88.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93911c569144d0a4e57cc6c44666d710a672db9619f4064959922ca80850bf1b
|
|
BLAKE2b-256 checksum How to use checksums |
ae03315298c5d9475f8aef93e2797b19b0ef89036a86551c4c603d1cba904e10
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.19
|
Release files / lauterbach_trace32_rcl-1.1.6-py3-none-any.whl
| Download URL | lauterbach_trace32_rcl-1.1.6-py3-none-any.whl |
|---|---|
| Size | 84.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
351c1368f19208d90ffdb743aeca12b28da7ce81a2498212f6a7834bf93c5897
|
|
BLAKE2b-256 checksum How to use checksums |
a32cbedf014d9fafa727096888856e28482cd531f223c24e7627c9ec3b92db39
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.19
|
Security for lauterbach-trace32-rcl 1.1.6
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.