guido wrote: > Here at BeOpen we're scrambling to get the release schedule for the > rest of Python 1.6 planned. We're now looking at releasing Python > 1.6b1 (or maybe it's going to be called 1.6a3 after all) on June 30! > This means that if SRE isn't ready, we'll go with an incomplete SRE. > Still better than no SRE! a major SRE patch is coming up later today. btw, what would it take for me to check it in myself (assuming someone will give me commit privs, of course)? can I apply patches via = sourceforge's web interface, or do I have to figure out how to run cvs over ssh etc = etc (tim? where's the second installment of your sourceforge vs. windows = series?) </F>
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