4 ms·

The problem is some of the massive python modules that cannot be ported from 2.7 to 3 .x

• viraptor 10y ago
  Which ones specifically? Many massive ones that held out for a long time are either done or in the process of porting. (twisted, openstack, almost all web frameworks, etc.) PS. https://python3wos.appspot.com/ https://python3wos.appspot.com/ now shows only few packages not marked as compatible from the most popular ones. One group (carbon, graphite, supervisor) are not libraries so they don't really affect others. The other is specific moz* libraries - and they're for Mozilla's internal testing, so nobody else should care that much.
  • unixhero 10y ago
    Yes I was thinking about twisted
• Tenobrus 10y ago
  Sure there are some, but several lists (for example, http://py3readiness.org http://py3readiness.org) show that over 95% of very popular packages support Python 3, and some only support Python 3. At this point while you might need 2 for some very specific purposes, 3 has the majority of important packages and new development.
  • unixhero 10y ago
    I stand corrected. I realize that it was 4 years ago, since I tried to learn Python ... And at that point in time key libraries, which I for instance read books to learn, twisted, was 2.7 only ...
• chx 10y ago
  As I mentioned elsewhere, my go-to example was PCSC-Lite support. I thought it so old and obscure it will never happen. But look, https://pypi.python.org/pypi/pyscard/1.9.4 https://pypi.python.org/pypi/pyscard/1.9.4