➜

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 larry
Recipients docs@python, larry, ncoghlan, petr.viktorin
Date 2015-09-08.12:32:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1441715541.93.0.737194118992.issue24937@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm the author of capsulethunk.h, and I am happy to relicense it under MIT.

How would you feel about leaving capsulethunk.h there, for posterity's sakes, but adding "for updates please see py3c"?  We could even update the capsulethunk.h there.  I'm not saying "we have to do it this way", I'm asking whether the users would be better served by leaving the example around vs removing it and forcing them to go looking on an external web site.
History
Date User Action Args
2015-09-08 12:32:21larrysetrecipients: + larry, ncoghlan, petr.viktorin, docs@python
2015-09-08 12:32:21larrysetmessageid: <1441715541.93.0.737194118992.issue24937@psf.upfronthosting.co.za>
2015-09-08 12:32:21larrylinkissue24937 messages
2015-09-08 12:32:21larrycreate