4 ms·

It's libraries rather than porting. Funnily, though, I just thought 'yeah there's that library I use, they never ported that', for one of my codebases. Just lo

by sago 11y ago

It's libraries rather than porting. Funnily, though, I just thought 'yeah there's that library I use, they never ported that', for one of my codebases. Just looked it up and they now have ported it. So I guess it's time for me to do the same. I wonder what proportion of (actually used) libs are Py 2 only still.

spdionis 11y ago
TensorFlow?
- CydeWeys 11y ago
  Python 3 support is literally issue #1: https://github.com/tensorflow/tensorflow/issues/1 https://github.com/tensorflow/tensorflow/issues/1 I suspect this is just an issue of they didn't want to block the release on not having Python 3 support ready at launch.
  - spdionis 11y ago
    The weird thing as a non-python user is why did they even start with python 2 as first class in mind?
    - anabranch 11y ago
      Probably the same reason (or at least somewhat related to) that Google App Engine only supports python 2.7. (https://cloud.google.com/appengine/docs/python/ https://cloud.google.com/appengine/docs/python/)
    - eeZi 11y ago
      Big companies are moving slow, even Google.
    - CydeWeys 11y ago
      Python 2 is used internally at Google, and TensorFlow is, I believe, an open sourcing and nicer packaging of something that has already existed internally for awhile.
    - vegabook 11y ago
      because the low risk, high-audience strategy, when you're launching a new product, is to follow the path of least resistance, rather than being dogmatic. Maximum audience.
ensignavenger 11y ago
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 :)
    - 11y ago

by sago 11y ago

spdionis 11y ago

TensorFlow?

CydeWeys 11y ago
Python 3 support is literally issue #1: https://github.com/tensorflow/tensorflow/issues/1 https://github.com/tensorflow/tensorflow/issues/1 I suspect this is just an issue of they didn't want to block the release on not having Python 3 support ready at launch.
- spdionis 11y ago
  The weird thing as a non-python user is why did they even start with python 2 as first class in mind?
  - anabranch 11y ago
    Probably the same reason (or at least somewhat related to) that Google App Engine only supports python 2.7. (https://cloud.google.com/appengine/docs/python/ https://cloud.google.com/appengine/docs/python/)
  - eeZi 11y ago
    Big companies are moving slow, even Google.
  - CydeWeys 11y ago
    Python 2 is used internally at Google, and TensorFlow is, I believe, an open sourcing and nicer packaging of something that has already existed internally for awhile.
  - vegabook 11y ago
    because the low risk, high-audience strategy, when you're launching a new product, is to follow the path of least resistance, rather than being dogmatic. Maximum audience.

ensignavenger 11y ago

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 :)
  - 11y ago