Collin Winter <collinw at gmail.com> writes: > On Wed, Nov 4, 2009 at 6:49 PM, Ben Finney <ben+python at benfinney.id.au> wrote: > > Okay. It's probably best for anyone with their Python developer hat > > on (which, in this forum, is all the time for any Python developer) > > to make the status of 3to2 clear when recommending it to people > > concerned about future plans. > > Are you implying that we shouldn't recommend 3to2 to people wanting to > develop in Py3k and back-translate to 2.x? No, I'm implying that mentioning Python 3, 3to2, and 2to3 all together in a discussion about how to migrate can easily give the false impression that they're all equally supported by the Python developers. That 3to2 is *not* supported officially is certainly something I'd want to know if a Python core developer was recommending it to me to reassure me about the migration path to Python 3, and I didn't get that impression from the way it's been casually referenced in this discussion. -- \ “Never express yourself more clearly than you are able to | `\ think.” —Niels Bohr | _o__) | Ben Finney
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