Here is an interesting website: http://py3readiness.org/
Not sure of its accuracy. I think the Python 3 "in trouble" issue might be solved in time. There aren't that many "BIG" packages that aren't Python 3 compatible. But in my experience it hasn't been the big packages (except gevent) that have forced a project back to python2, it's more obscure packages that you don't want to have to do without. Hence the time part. Even in the python community eventually somebody will reinvent the wheel. Smaller packages are also eventually abandoned. I think there is sufficient pressure for *new* libraries to be Python 3 compatible. At this point the most harm to Python 3 would come if Guido caves to the pressure and allows continued development and support (outside of security updates) to Python 2. On Tuesday, May 5, 2015 at 10:23:08 AM UTC-4, Edward K. Ream wrote: > > Leonistas should not typically *ever *have to change their existing Leo > scripts or plugins. > > However, that's too restrictive, so I'll amend that to say that I'm > willing to make code incompatible only if I personally am willing to change > all official plugins to support the change. I think that strikes the right > balance. > > Now for the Off Topic part... > > You could say that Python follows that philosophy by providing the 2to3 > tool, but that tool doesn't seem to be enough. If it were, the Python > Software Foundation could simply convert missing packages themselves ;-) > > My sense is that Python 3 isn't being adopted as quickly as Guido would > like. Perhaps what is missing is a tool to create a unified code base. > Say 2to3 followed by a merge of the old and new code bases. Or something > like that. > > *Speculation*: Python 3 might actually be in trouble. Maybe Python 2 and > 3 are sufficiently different languages that no reasonable tool can actually > bridge the gap. Guido would likely disagree, but I'm starting to wonder... > > The incompatibility of Python 2 and 3 is certainly impeding progress. For > example, function annotations <https://www.python.org/dev/peps/pep-3107/> > are syntactically invalid in Python 2, so Leo's unified code base can't use > them. This is most annoying. > > Your comments please. The off-topic lamp is lit. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
