For now I think I can just checkout the commit before the merge.
Yup, this is a reasonable solution for now. It is possible to make the blake2b-py install optional and maintain the pure python implementation as a backup. It's probably not top priority for us, but if you open an issue or want to work on it yourself I'm happy to guide on the necessary steps.
the pyethash version this depend on seems to have a problem compiling on big endian platforms. This issue was fixed in the pyethash repo but I don't think that fix was put onto pypi, so the version pip tries to install fails.
Can you link to the issue or the fix in the repo? I can push out a release, just want to make sure I understand the change you need so I can verify it's working, before release.
py-evm0.2.0a43+ under the hood)
eth-testerv0.2b3 I believe
towncrier --draftis my friend. ^_^
ethereum-python-project-templateethereum/ethereum-python-project-template#28 but we wanted to wait for the next Trinity release to see if there are any further tweaks to the release script needed.
Turns out fragments from the misc category don't get their contents displayed, they just get the numbers listed in a "Miscellaneous internal changes" section.
Yeah, as far as I know, someone did this intentionally. I added an "internal" section to trinity that shows towncrier content here: https://github.com/ethereum/trinity/blob/62a85b1d3c89908c37fd62d9c4370dc8e3b139e2/pyproject.toml#L34-L37 -- the idea is that it's only of interest to contributors rather than users. Then misc would be for trivial changes, like maybe changing flake8 rules and updating the repo. @veox