Fix bad initializer
Do not crash when asked to export private keys
Fix behavior when calling get_master_public_key from an external context
setup.py: Install qrscanner (it's a library now)
Merge pull request #856 from btchip/fixerrorsigning

Fix bad initializer
Merge pull request #857 from btchip/deny_export_private_key

Do not crash when asked to export private keys
Merge pull request #858 from btchip/labelfix

Fix behavior when calling get_master_public_key from an external context
Merge pull request #859 from PabloCastellano/master

setup.py: Install qrscanner (it's a library now)
Update Japanese wordlist

1. First 3 characters are all unique now.
2. smallest word is not 3 characters long.
Merge pull request #877 from dabura667/update_jpwlst

Update Japanese wordlist
use certs from request module in interface.py
Merge branch 'master' of git://github.com/spesmilo/electrum
rm print statement
Fix "Invalid Fee" issue when start with fiat in send (exchange rate plugin)

Problem:

Using the exchange rate plugin in the send dialog one can start with
entering a fiat amount, e.g. 5 USD, and the BTC amount is updated,
but no fee is calculated.

In this case can get "Invalid fee" error until the BTC amount is
touched manually and fee is calculated. This can cause confusion
when "set transaction fees manually" is disabled.

Reproducing:

* enable exchange rate plugin
* start Electrum
* in send dialog fill out any receive address
* add a value (e.g. 5) into the fiat dialog and see the BTC value filled out
* fee is not filled out, or if disabled the manual transaction fees then directly
  get "Invalid Fee" error

Expectation:

* Fees are calculated just as it would be by filling out the BTC field

Fix:

Fixed by triggering a fee setting the same way as it is done when
the BTC field is edited, by calling `textEdited.emit("")` of the relevant
`BTCAmountEdit` element. One problematic  thing is that this also triggers
a change on the fiat we just edited, and thus cursor positions need to be saved
and restored. This is not ideal, there should be a way to avoid such cascades
and trigger fee calculation directly instead of by proxy.

Editing the fiat field with these changes is more or less okay, there can be
some strange steps when the decimal point is edited, but IMHO not worse
than the BTC field when the decimal point is edited there.
Merge pull request #878 from imrehg/fee

Fix "Invalid Fee" issue when start with fiat in send (exchange rate plugin)
Merge branch 'master' of https://github.com/spesmilo/electrum into clean