With Python upgraded to 3.9 replaced the random_bytes
function in util of functional tests and replaced it’s usage with random.randbytes
.
Closes #28720.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
For detailed information about the code coverage, see the test coverage report.
See the guideline for information on the review process.
Type | Reviewers |
---|---|
ACK | maflcko, BrandonOdiwuor, stickies-v, kristapsk |
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
93@@ -94,8 +94,7 @@
94 from test_framework.test_framework import BitcoinTestFramework
95 from test_framework.util import (
96 assert_raises_rpc_error,
97- assert_equal,
98- random_bytes,
99+ assert_equal
,
?
39@@ -39,8 +40,7 @@
40 assert_greater_than_or_equal,
41 assert_raises_rpc_error,
42 find_output,
43- find_vout_for_address,
44- random_bytes,
45+ find_vout_for_address
ACK fe3ac3700d31a6329056fee983d91dd8e4c987c1, thanks for picking this up
nit for future reference: no need to mention the issue number (28720) in the commit message, it causes a bit of github spam and this change is self-explanatory. It can be good practice for more complex commits to point the reader towards additional resources (but even then, commits are ideally self-explanatory)