Substrate-interface

Latest version: v1.7.8

Safety actively analyzes 630217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 23

1.0.4

Not secure
Changes

* Fixed issues decoding/encoding nested Calls 143
* Skip unnecessary type conversion for scale_info type registries (performance boost `MetadataV14`)
* Fixed issue with decoding certain `Compact` types

**Full Changelog**: https://github.com/polkascan/py-substrate-interface/compare/v1.0.3...v1.0.4

1.0.3

Not secure
What's Changed
* Fixed incorrect reload of type registry when PortableRegistry is present
* Fixing calculation of total fee amount when event is a balances/deposit by ilkericyuz in https://github.com/polkascan/py-substrate-interface/pull/142
* Fixed MetadataV14 block author retrieval 138
* Fixed exception when event had no attributes
* Fixed exception when Call has no args
* Pallet index is explicitly stored in metadata
* Added alias for type xcm::latest::Outcome
* Incorrect processing of BTreeMap types in MetadataV14

**Full Changelog**: https://github.com/polkascan/py-substrate-interface/compare/v1.0.2...v1.0.3

1.0.2

Not secure
Kusama and Rococo type registry update

1.0.1

Not secure
Added Contract compatibility with MetadataV14 runtimes

1.0.0

Not secure
| ⚠️ This new major release is not fully backwards compatible with v0.13 releases |
|-----------------------------------------|

Support for `MetadataV14` and `PortableRegistry`.

It has the following breaking changes:

- All properties of `Struct` SCALE-objects in existing type-registries are now converted from CamelCase to snake_case, to be compatible with generated `PortableRegistry` structs
- `scale_obj.value` always contains a serialised version in Python primitives
- `scale_obj.serialize()` will contain a human readable format
- `scale_obj.value_object` contains the full nested SCALE objects if applicable. A short-hand of `scale_obj.value_object[‘accounts’].value_object[0].ss58_address` is `scale_obj[‘accounts’][0].ss58_address`. If the `scale_obj` is a `Vec` this will also act as an iterable.
- Reformatting of value attributes of many `ScaleType` classes; in particular `Extrinsic` and `Event`
- Metadata decoding has been completely refactored and should use `MetadataVersioned` in stead of removed `MetadataDecoder`
- Output format of metadata functions changed
- All `ScaleType` classes moved to `types` sub-package; `block` sub-package is removed

1.0.0a2

Not secure
| ⚠️ This alpha release is not backwards compatible with earlier releases |
|-----------------------------------------|

This version is a pre-release and compatible with upcoming `MetadataV14` and `PortableRegistry`.

It has the following breaking changes:

- All properties of `Struct` SCALE-objects in existing type-registries are now converted from CamelCase to snake_case, to be compatible with generated `PortableRegistry` structs
- `scale_obj.value` always contains a serialised version in Python primitives
- `scale_obj.serialize()` will contain a human readable format
- `scale_obj.value_object` contains the full nested SCALE objects if applicable. A short-hand of `scale_obj.value_object[‘accounts’].value_object[0].ss58_address` is `scale_obj[‘accounts’][0].ss58_address`. If the `scale_obj` is a `Vec` this will also act as an iterable.
- Reformatting of value attributes of many `ScaleType` classes; in particular `Extrinsic` and `Event`
- Metadata decoding has been completely refactored and should use `MetadataVersioned` in stead of removed `MetadataDecoder`
- Output format of metadata functions changed
- All `ScaleType` classes moved to `types` sub-package; `block` sub-package is removed

Page 9 of 23

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.