which is sort of a one-file randomness library. Idon't think it depends on any bitcoin specific things
e.g. user created containers and chroots won't have the /dev/urandom device, some sandboxes (such as cluodabi/capsicum) don' t have file access at all (not that we can support those at the moment in bitcoin core). Direct system calls are the new way to get randomness from the OS.
Wladimir J. van der Laan (Bitcoin Core binary release signing key) <firstname.lastname@example.org> 01EA 5486 DE18 A882 D4C2 6845 90C8 019E 36C2 E964 is expired
wumpus: the original reason I brought it up, was translators confusing it for "About Bitcoin-Qt". but that has since been resolved in other ways, so
I think all this is kind of pointless, user use of bitcoin is dying because of sync resource requirements.
I think that would be dandy. I dunno what about Bitcoin would say.
so the menu would have About Bitcoin Core and About Bitcoin; and the former's dialog have a link for About Qt?
luke-jr: It might be better to put the QT link though on the about bitcoin core page though.
re "About Qt": we're using "About %1" now anyway, so the translation issue is presumably gone, and Qt might actually be worth promoting anyway; thinking perhaps what would be an improvement there is to add an "About Bitcoin" :p
well if the first line contains python3 it should be run with python 3, lacking that there is no general way to detect whether code is python2 or python3. But believe me, the bitcoin core python scripts need to be run with python 3.
you should run all the bitcoin core scripts with python 3
jonasschnelli: My preference would be to also move the bitcoin-util-test.py and bctest.py (and data for those tests) from src/test to whatever you rename qa to. Those tests seem much more like the integration tests in qa than the unit tests in src/test
gmaxwell: re: VM image being snapshotted and restored, that's basically a case where reusing a secret is by itself harmful - is there an example in Bitcoin where that's the case, now that we do deterministic signing?