You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Should licence headers be turned into docstrings or remain a comments? #1435
That's the question arisen by recent rebase I've done (7f96b36). Some modules taken from third party (like namecoin or network.asyncore_pollchoose) have the licence headers which were turned into docstrings by @coffeedogs. Though I've seen a python packages with similar formatting style (like jsonrpclib) I still don't understand the reason to have the licenses in documentation.
Let's clarify the bitmessage's style guide in this case.
Activity
g1itch commentedon Nov 21, 2019
I assume they should remain comments or turned back into comments.
g1itch commentedon Dec 20, 2019
I see it again in #1554
PeterSurda commentedon Jan 10, 2020
I would say we add licenses of individual files into the
LICENSEfile in project root.