Skip to content

Releases: multiversx/mx-sdk-py-cli

v6.2.1

22 May 09:56
475f787

Choose a tag to compare

What's Changed

Full Changelog: v6.2.0...v6.2.1

v7.0.0b0

19 May 13:41
2ba27be

Choose a tag to compare

v7.0.0b0 Pre-release
Pre-release

What's Changed

Full Changelog: v6.1.3...v7.0.0b0

v6.2.0

19 May 12:15
f0437fc

Choose a tag to compare

What's Changed

Full Changelog: v6.1.3...v6.2.0

v6.1.3

20 Mar 08:12
f01907b

Choose a tag to compare

What's Changed

Full Changelog: v6.1.2...v6.1.3

v6.1.2

16 Mar 12:53
11d6413

Choose a tag to compare

What's Changed

Full Changelog: v6.1.1...v6.1.2

v6.1.1

14 Mar 15:48
1dc8a81

Choose a tag to compare

What's Changed

Full Changelog: v6.1.0...v6.1.1

v6.1.0

14 Mar 11:42
d7a7f81

Choose a tag to compare

What's Changed

Full Changelog: v6.0.1...v6.1.0

v6.0.1

20 Feb 16:29
1b2faf1

Choose a tag to compare

What's Changed

Full Changelog: v6.0.0...v6.0.1

v6.0.0

17 Feb 12:25
5a20d32

Choose a tag to compare

Moved wallet-related functionality (commands kept intact)

Removed wallet sub-package from multiversx_sdk_cli, since all the wallet-related functions are now defined in multiversx_sdk_wallet. Thus, from now on, mxpy relies on multiversx_sdk_wallet to implement it's functionality for managing wallets and signing transactions.

Let's state this again: multiversx_sdk_cli should not be used as a Python library anymore, but only as a CLI tool - under the nickname mxpy. That is, you should not import multiversx_sdk_cli in other Python tools, packages or scripts. Import multiversx_sdk_core, multiversx_sdk_wallet and multiversx_sdk_network_providers, instead.

Experimental, partial support for Windows

BASH shell required, though (at least for installation).

Users can now use the mxpy-up facility to install mxpy in Windows, outside of WSL. However, Windows support is experimental and partial at the moment. Contract builds aren't available yet (due to a few issues related to the Rust installation) - they will be in a future version, however. Transaction creation / broadcasting and wallet utilities are available.

Allow one to alternate between Rust installations

Allow one to specify the desired resolution strategy for some dependencies: rust, go and wasm_opt.

Available resolution strategies are:

  • SDK - resolve dependency from ~/multiversx-sdk
  • host - resolve dependency as already installed on the host machine (e.g. which {dependency} should output a valid path).

Example in ~/multiversx-sdk/mxpy.json config:

"dependencies.rust.resolution": "SDK",
...

Example for switching the resolution strategy using the CLI:

mxpy config set "dependencies.rust.resolution" "host"

PATH not altered by default anymore by mxpy-up

In mxpy-up, we do not alter the PATH variable by default anymore; that is, we do not alter .profile, .zshrc or .bash_profile automatically anymore. The user has to explicitly demand this (during the installation script).

List of PRs

Full Changelog: v5.3.2...v6.0.0

v6.0.0b4

16 Feb 18:30
5b4b8a0

Choose a tag to compare

v6.0.0b4 Pre-release
Pre-release

Full Changelog: v6.0.0b3...v6.0.0b4