[MAL] > Instead, we should come up with a way which satisfies the licenses. > Since most licenses require a copy of the text to be included in > the documentation, I think the easiest and most reliable way of > achieving this is to add a new licenses section to the documentation > and Python's LICENSE file itself (Latex allows including text from > other files in the docs, so adding new licenses to the LICENSE file > would suffice if LICENSE is included verbatim in the Latex docs). This seems to be the most straight-forward way to go. If everyone agrees, I'll start the ball rolling by adding the verbatim text for the MersenneTwister code. Raymond Hettinger
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