News for hackers. Stuff that matters.
Re:Propel – Machine learning for Javascript by cjalmeida on Monday February 26, 2018 @02:18PM (#16468110)
There's no python vs python3 decision to make. There's no (sane) reason to pick Python 2 in 2018 for new projects.

Conda installer comes with Python prepackaged. So it's really a single exe and one CMD to get a Tensorflow env setup. And, of course, you have access to numpy, pandas, jupyter, PIL ...

Re:Propel – Machine learning for Javascript by jopsen on Monday February 26, 2018 @02:30PM (#16468213)
+ virtualenv

I always forget to set that up. Also I never learned python packaging, with npm it was trivial.

Re:Propel – Machine learning for Javascript by woolvalley on Monday February 26, 2018 @04:39PM (#16469205)
The basic rule of thumb is npm is 'virtualenv by default' while pip is 'global by default'.
Re:Propel – Machine learning for Javascript by JBReefer on Monday February 26, 2018 @05:27PM (#16469553)
This kind of thing is why people are saying npm is easier...
Re:Propel – Machine learning for Javascript by 3131s on Monday February 26, 2018 @10:47PM (#16470936)
Yes, npm installs libraries locally so it avoids the need for something like virtualenv in the first place. Coming from Python, that immediately struck me as a better approach to package management.
Re:Propel – Machine learning for Javascript by cx1000 on Tuesday February 27, 2018 @02:08AM (#16471614)
If you use pipenv it takes care of the virtualenv stuff behind the scenes for you.
Re:Propel – Machine learning for Javascript by darknoon on Sunday March 11, 2018 @01:53PM (#16563987)
You say this, but coremltools (convert from industry standard to Apple's ML framework) initially only supported python 2, so it was annoying to work with some code in Python 2 and some in 3.5.
Re:Propel – Machine learning for Javascript by partycoder on Monday February 26, 2018 @11:57PM (#16471171)
ES5 and ES6 differ a lot. There's reverse compatibility, but they do differ.