This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author toddrjen
Recipients docs@python, terry.reedy, toddrjen
Date 2020-03-16.02:34:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584326097.23.0.90226650469.issue39883@roundup.psfhosted.org>
In-reply-to
Content
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.
History
Date User Action Args
2020-03-16 02:34:57toddrjensetrecipients: + toddrjen, terry.reedy, docs@python
2020-03-16 02:34:57toddrjensetmessageid: <1584326097.23.0.90226650469.issue39883@roundup.psfhosted.org>
2020-03-16 02:34:57toddrjenlinkissue39883 messages
2020-03-16 02:34:56toddrjencreate