On 7/22/2010 9:36 AM, stefan brunthaler wrote: >> Depending on the size and complexity of the >> patches, it may still be worth exploring for 3.2. If your work speeds CPython, U.S. would have to be even better to knock it out. > I am currently not aware of the planned release schedule, but I think > that some of the techniques could very well be released in 3.2 -- with > a conditional compilation target similar to the computed-goto feature. 2.6.6 is scheduled for August. 3.2 releases should start thereafter with a December target. On licenses. Look for the contributor agreement on the site. It says that you license your code on a non-exclusive basis to the PSF under one of two licenses. Both allow PSF to relicense and redistribute your code as part of a Python release. I recommend you print it out and, as someone else suggested, check with your advisor/university as to whether there is any problem with you contributing the software under one of*those particular licenses*. -- Terry Jan Reedy
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