On 9 September 2015 at 17:16, Steve Dower wrote:
> Don't bother reading into SxS assemblies. It may work, but it will destroy
> more brain cells than are worth wasting on it. :)
:-) Yeah, I looked at SxS once before and sprained my brain. But the
summary on the numpy wiki looked like a digestible
On 09Sep2015 0819, Paul Moore wrote:
On 9 September 2015 at 16:11, Carl Kleffner wrote:
A good overview on this topic is given on
https://github.com/numpy/numpy/wiki/windows-dll-notes. As a side note the
PATH is usually the latest place in the search order of DLLs. Pre-loading
python35.dll into
On 9 September 2015 at 16:11, Carl Kleffner wrote:
> A good overview on this topic is given on
> https://github.com/numpy/numpy/wiki/windows-dll-notes. As a side note the
> PATH is usually the latest place in the search order of DLLs. Pre-loading
> python35.dll into the process space from within v
A good overview on this topic is given on
https://github.com/numpy/numpy/wiki/windows-dll-notes. As a side note the
PATH is usually the latest place in the search order of DLLs. Pre-loading
python35.dll into the process space from within vim could be a possible
solution.
2015-09-09 16:30 GMT+02:0
First of all, an apology. I know this is probably going to be of
limited interest for many on python-dev, but I'm honestly not sure
where there's a better audience for the question. As it's related to
how people should use the new "embeddable" distribution of Python 3.5,
I'm hoping it's sufficientl
