News for hackers. Stuff that matters.
Re:Python JITs are coming by smallnamespace on Tuesday August 23, 2016 @01:22PM (#12345454)
It seems the scientific bits of Python have been moving at a much faster development pace though. Do you have any insight as to why?

Personally, I started using Anaconda for everything and just drop down into pip when I find a package that isn't in there already, and it's been working very well.

Re:Python JITs are coming by synparb on Tuesday August 23, 2016 @01:27PM (#12345511)
You should also check out https://conda-forge.github.io/, which is building high quality, community curated conda packages for a lot of stuff that isn't available from the main Continuum channel.
Re:Python JITs are coming by drauh on Tuesday August 23, 2016 @02:04PM (#12345918)
For scientific work, I find it worth the effort to compile from source using Intel compilers + MKL (or a compiler + math library that can optimize well for your particular hardware platform).
Re:Python JITs are coming by wclax04 on Tuesday August 23, 2016 @07:24PM (#12348587)
aren't all of the default conda channel packages compiled with MKL now?
Re:Python JITs are coming by fijal on Tuesday August 23, 2016 @01:35PM (#12345601)
I'm not really commenting on the relative merits of the technology or who should use what. It's about the lack of admission that there is other stuff and other requirements
Re:Python JITs are coming by stuaxo on Tuesday August 23, 2016 @03:08PM (#12346549)
Hm, I would consider using Anaconda if it worked for Gtk libraries (GEGL etc) on all 3 platforms (yeah I know this is hard outside Anaconda too).