-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use BSD0 license for code in docs #84064
Comments
Currently using code examples and recipes from the documentation is complicated by the fact that they are all under the Python 2.0 license. Putting them under a more permissive license, particular the BSD0 license, would make them much easier to use in other projects. |
What is the complication? The Python license is already rather permissive. Anyway, there is a [email protected] address for trademark issues, listed on the site, and it might be appropriate for license legal questions also. Or this might be a question for discuss.python.org. |
Hi Terry, Please take a look at the linked PR. This was already discussed on the python-ideas mailing list and Guido agreed this is a good idea. It is currently waiting on a PSF board decision. Guido requested I create a blurb, and that required a corresponding issue number, so I created this issue. But to answer your question, the problem is incorporating code into an existing project. The whole point of examples and recipes is that they be used in other projects. But keeping them under the Python 2.0 license makes this hard, since it requires all the documentation keep that same license. So you can't use, say, an itertools recipe without keeping a separate license for that code, and some way to identify which code falls under that license. |
OK. I looked at the PR. Normally, issue comes first, with justification and approval status. |
FWIW the PSF board approved the change. |
Todd, you have a PR for the pydotorg repo as well, right? Can you link it here? |
The pull request is It doesn't seem to went let me add it to linked pull requests. |
This looks fully resolved. Thanks again Todd! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: