Jason Carver
Jason Carver
The workaround I've been using is `ptw mymodule/ tests/ -- --failed-first --exitfirst` in order to quickly re-loop on failing tests, but run all the remaining tests. ( or `ptw mymodule...
`-x` halts at the first failed test, which may mean that multiple previously failing tests are run (if they start passing).
Say you have tests A, B, C, D, run in that order. Then you break tests B-D. The next run is: - A - pass - B - fail -...
> Every single broadcast ends up involving a couple of expensive network lookups... "expensive _disk_ lookups"?
Weird, I have no idea why this showed up in my "participating" notifications today. I'll see myself out...
Hm, I don't think this particular test exists yet in eth-account. Maybe copy/move the issue over and reopen?
Here's a first pass at a new `Keystore` API: ```py from eth_account import Keystore # or maybe from eth_keystore import Keystore? locked_accounts = {} for keydict in Keystore.load('~/.mykeystorefiles'): locked_accounts[keydict['address']] =...
It's probably best to open a new issue to discuss, @AndreMiras
Issue #80 looks like the same thing.
Even safer: the DApp could wait for the user to confirm that they've saved the bid info before sending the transaction (like myetherwallet.com)