Should licence headers be turned into docstrings or remain a comments? #1435
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-22#1435
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello!
That's the question arisen by recent rebase I've done (7f96b36). Some modules taken from third party (like
namecoin
ornetwork.asyncore_pollchoose
) have the licence headers which were turned into docstrings by @coffeedogs. Though I've seen a python packages with similar formatting style (likejsonrpclib
) I still don't understand the reason to have the licenses in documentation.Let's clarify the bitmessage's style guide in this case.
I assume they should remain comments or turned back into comments.
I see it again in #1554
I would say we add licenses of individual files into the
LICENSE
file in project root.