Skip Montanaro wrote: > Ah, but now you have a "machine" that will generate the bit of documentation > you desire as part of the install process (binary or source). The question still is what is easiest for people producing Python binaries. Do they want to paste files from the CVS to fulfill the requirements, or would they prefer to print a variable in Python? I agree with Raymond that collecting the statements alone in copyright won't help, since it does not meet the licensing criteria of some of the licenses. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4