When I first started doing this kind of thing, there were like two Tory Lawsons on the internet, one of whom was I think actually a Victoria. Now there are lots of us, and I am sorry if you were looking for one of the other ones. We have an annual retreat thing, so if you want to get a hold of one of the others, let me know.
Everything I read online suggested that to fix this situation I needed to build it from source, which meant installing compilers for C++ and Fortran, Cygwin, MinGW, and other stuff, none of which I actually want on that machine. There are Python distributions that already have SciPy working, but if you already have Python installed and are happy you may not want to mess with those. The answer for my situation wound up being that I had to dump the version of NumPy I was using and get the NumPy-MKL package instead, which contains the libraries mentioned in the above errors thanks to Intel's Math Kernel Library. So, here are the steps I eventually found to allow me to use SciPy with my existing Python environment without building it from source.Continue reading →
Our Visual Studio project contains a build step in which it copies files to a mapped drive, and we got funky behavior after the team upgraded to Windows 10. This behavior basically made it look like the destination wasn't there or that we didn't have access to it.Continue reading →