Lennart Regebro writes: > 2009/6/7 Stephen J. Turnbull <stephen at xemacs.org>: > > Python's 2.x/py3k division is a tour de force; I still can't believe > > my eyes that you've pulled it off. > > Well, It's not pulled off until Python 3 has surpassed Python 2 in > usage. I'm referring only to the management of the dual-trunk workflow, not to whether Python3 will be the preferred path for the future. That workflow has its problems, but still it seems very successful in keeping what needs to be synced, synced, and what needs to be different, different.
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