nano

The instructions and infrastructure for building on windows are not very good. It takes too long and there are too many manual steps and too much ambiguity and it takes too long between each manual step. We need to do better. I followed the instructions at build options on nano.org. I did not try to follow the steps taken by the CI build which maybe would been better because at least there would b

Please write shortest code example for this question:
How to parse xml in python

How to do it:

1. Go to python codes
2. Create new file (named in underscore case, should contain key words from title) with md extension (markdown file).
3. Propose new file with following content (please use all three blocks if possible - title

⭐️ S (situation) ⭐️

You don't need to discuss code changes about formatting: indents, spaces or tabs, etc

⭐️ T (task) ⭐️

The developer will add code changes with declared formatting which is available in Prettier config

⭐️ A (action) ⭐️

Add Prettier with https://prettier.io/

⭐️ R (result) ⭐️

It will autochange files and format them correctly for the project

Version: 0.9.10 (Google Play)

The password field on the Canoe lockscreen doesn't use all the space that is available, it only goes to about the middle. This can get quite annoying when you enter long passwords because you can't see if you continued typing. Here is a screenshot:

Right now there's no way of seeing a wallet's phrase or private key via the CLI. The private key is visible via the wallet file, but not the phrase--it uses an Entropy rather than saving the words.

It would be good to have a command, e.g.:

> feeless wallet secret --id

The output would vary depending on the wallet type:

> feeless wallet secret --id xxx # phrase, must match