Conversation
Reference to Python PEPs accidentally left in.
|
Thanks for actually reading BIP 1 :) As I've complained before, it's probably the least read 'important' document in bitcoin history. Shameful ACK TBH I think you can remove "code style" completely there, BIPs hardly contain code, and if they do (as BIP66 does) there's no code style guideline. |
@laanwj "BIPs hardly contain code, and if they do (as BIP66 does) there's no code style guideline"
|
ACK 291e670 |
|
@laanwj Good point. Updated the pull request to reflect that. I maintain that Bitcoin documentation is a bit disjointed. All my pulls into core have been around trying to make stuff more readable. If more people need to read it, needs to be more visible. |
|
BIP 1 allows me to reassign BIPs if authors go missing. However, I consider BIP 1 set in stone, and instead would prefer if people make the effort to review BIP 2 as a replacement, which I will be proposing to the mailing list shortly, if there are no further review comments. |
|
@luke-jr @genjix Is clearly MIA, so #412 and #453 are in limbo. So to be clear you don't plan on reassigning BIP 1 to another author, but instead plan on trying to get BIP 2 accepted? If so #412 and #453 can probably be closed if/when BIP 2 is accepted. Is there a current discussion area for BIP 2? I'd like to make some comments. |
Right now you could send your comment to https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-September/013165.html |
|
BIP 1 has been Replaced by BIP 2. |
This document was derived from PEP-0001. This line makes reference to BIPs 8 and 7, which don't exist. These are leftover refrences to Python PEPs which establish guidelines for code styles.