At 11:10 PM 1/10/2007 +0000, Paul Moore wrote: >On 10/01/07, glyph at divmod.com <glyph at divmod.com> wrote: > > I've been assuming for some time that the only hope for Py3k compatibility > > within Twisted would be using PyPy as a translation layer. > >Does this ring as many warning bells for me as it does for others? I >know very little about the current state of PyPy, but I read your >comment as implying that you expect Twisted to be unavailable (at some >level or other) for users of Py3K. Is that right? > >How many other projects/packages anticipate *not* migrating to Py3K, I wonder? I think it's safe to say that any package of comparable size is going to think twice about it without transitional compatibility.
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