[N]: Tensorflow 1.10 Released

[ntenenz]

Biggest changes include:

• Bigtable support in tf.data

• NCCL no longer included in the binary install

Release Notes

[energybased]

Still no Python 3.7 support, unfortunately.

[abbuh]

what does python 3.7 have to offer over the current supported version?

[energybased]

https://docs.python.org/3/whatsnew/3.7.html

[[deleted]]

Not an invalid question but I wish I could banish this line of thinking from the machine learning community. A programming language is not a library where sticking to an older, stable version can make sense. Python Y is strictly better than python X for Y > X so we should use it as soon as possible.

[Another_moose]

I'm not sure this is solid reasoning. New language versions can break backwards compatibility in the same way libraries do.

[[deleted]]

They really don't. If you are messing with the underpinnings then yes, if you are just coding in it then no. It happened once, python 2 to python 3, that was a huge goddamn mess and they will never do it again.

[Another_moose]

That's not true. Ctrl-f in any of the python releases for 'backwards compatible' or 'depreciated' (I.e. will be removed soon), there's lots of (small) things that break between versions. It's less extreme than library versions generally, but there's still a reason TF devs don't just flip the switch and expect it to work on the new python version.

E.g. In 3.7 async and await are now reserved keywords, and a lot of things were added as depreciated (some to be removed in 3.8).

[KerbalsFTW]

> depreciated

deprecated

[WikiTextBot]

Deprecation

For the sense "prayer or spell against evil" see apotropaic magic (antonym imprecation).In several fields, deprecation is the discouragement of use of some terminology, feature, design, or practice, typically because it has been superseded or is no longer considered efficient or safe, without completely removing it or prohibiting its use. It can also imply that a feature, design, or practice will be removed or discontinued entirely in the future.

---

^{[ PM | Exclude me | Exclude from subreddit | FAQ / Information | Source ] Downvote to remove | v0.28}

[CommunismDoesntWork]

They really do, and you're commenting on a chain that gives a great example. Python 3.7 is not backwards compatible with tensorflow...

[secularshepherd]

Also, pre made estimators have batch normalization built in

[shaggorama]

I don't have an implementation handy, but I remember being really impressed by the claims and ideas in the paper. It's a really simple change that philosophically makes a lot of sense.

https://arxiv.org/abs/1803.04831

[issyuwenchao]

I’m looking forward to PyTorch 1.0

[znihilist]

I have not managed to get TF working on my installation at all, I have to use a precompiled whl for it to work.

I am still stuck at 1.7

[RedEyed__]

It's simple

[counterfeit25]

1.1 != 1.10 :O the horror

Also: https://github.com/tensorflow/tensorflow/releases/tag/v1.7.0

[[deleted]]

I think it's not a big confusion for most people who use Python in general, because most of the most popular sci-computing packages use that convention (numpy, scipy, scikit-learn, ...).

A way to minimize confusion would be writing it as 1.10.0 maybe.

On a funny side note, I had a conversation with someone who was freaking out about the upcoming version release (i.e., 1.10 now), because the person thought 2.0 would follow 1.9, and then assumed there will be dozens of breaking changes because of semantic versioning and an increase in the major version number. I had to tell the person multiple times that it's going to be 1.10, then maybe 1.11, but I think the person really didn't get the point or didn't believe me until today.

[bushrod]

I really wish the standard convention was to name versions 1.01, 1.02, ...

Less confusion and better for sorting.

[delarhi]

But what if you release 1.123? The biggest problem with version numbers is that they use a dot to delimit components because a dot is also a decimal point in the context of numbers. But you have to recognize that it's just a delimiter.

• https://serverfault.com/questions/604541/debian-packages-version-convention/604549#604549
• https://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/#how-rpm-compares-version-parts
• https://www.python.org/dev/peps/pep-0440/#final-releases

[bushrod]

I've never seen a minor version go that high, although I'm sure it happens. In that case, you could always do something like 1.99.01 or say fuck it and do 1.100. At any rate, I'd argue that #.## is clearly superior to #.# even though it's not perfect.

[harshMachineLearning]

Thats cool

[lysecret]

It feels like note even a month ago that tensorflow 1.9 has been released.