4 ms·

At this point very few 'actually used' (meaning, used by more than a handful of organizations at most) are Py2 only. There are a few still in the process of po

At this point very few 'actually used' (meaning, used by more than a handful of organizations at most) are Py2 only. There are a few still in the process of porting, and a few that will never be ported due to being replaced (but are still somewhat popular for one reason or another.) For those who don't know: http://python3wos.appspot.com/ http://python3wos.appspot.com/

thrownaway2424 11y ago
People are still releasing brand-new Py2-only libraries to this very day. This is especially true in science, math, nlp, ml, etc.
- zardeh 11y ago
  Such as.... The entire scipy stack, ntlk, tensorflow has partial 3.0 support and plans to support both, caffe, theano, etc. There are few to no libraries that don't support, or don't plan to soon support both.
  - ensignavenger 11y ago
    I thought you were listing examples of libraries that didn't support Py3... so I was gathering links to refute your claims... then I realized you were posting examples in support of my claim that Py3 support is the norm :)
- ensignavenger 11y ago
  Yes, and I kinda think it is silly, but whatever. Care to share any examples of recent releases? I know Google's TensorFlow was/is Py2 only, but a Py3 release is imminent. Google has an unfortunate habit of using Py2... I can understand they have their reasons... it is a bit irritating though :) (Edit: Not that I care what they use internally... but sometimes they release a really cool open source library and it is Py2 only... arr! But at least they are sharing, so I can't really be too upset :)
  - progval 11y ago
    snap-python. Development started in 2013, and yet they refuse to support Python 3: https://github.com/snap-stanford/snap-python/issues/52 https://github.com/snap-stanford/snap-python/issues/52
    - eeZi 11y ago
      So you'll have to convince them. Maybe they did not realize that SWIG supports Python 3 nowadays? There's really no good reason not to support Python 3, and projects which refuse will at some point be forked.
      - daveguy 11y ago
        Nah, just do the smart thing and stick with python 2.7.

thrownaway2424 11y ago

People are still releasing brand-new Py2-only libraries to this very day. This is especially true in science, math, nlp, ml, etc.

zardeh 11y ago
Such as.... The entire scipy stack, ntlk, tensorflow has partial 3.0 support and plans to support both, caffe, theano, etc. There are few to no libraries that don't support, or don't plan to soon support both.
- ensignavenger 11y ago
  I thought you were listing examples of libraries that didn't support Py3... so I was gathering links to refute your claims... then I realized you were posting examples in support of my claim that Py3 support is the norm :)
ensignavenger 11y ago
Yes, and I kinda think it is silly, but whatever. Care to share any examples of recent releases? I know Google's TensorFlow was/is Py2 only, but a Py3 release is imminent. Google has an unfortunate habit of using Py2... I can understand they have their reasons... it is a bit irritating though :) (Edit: Not that I care what they use internally... but sometimes they release a really cool open source library and it is Py2 only... arr! But at least they are sharing, so I can't really be too upset :)
- progval 11y ago
  snap-python. Development started in 2013, and yet they refuse to support Python 3: https://github.com/snap-stanford/snap-python/issues/52 https://github.com/snap-stanford/snap-python/issues/52
  - eeZi 11y ago
    So you'll have to convince them. Maybe they did not realize that SWIG supports Python 3 nowadays? There's really no good reason not to support Python 3, and projects which refuse will at some point be forked.
    - daveguy 11y ago
      Nah, just do the smart thing and stick with python 2.7.