These are chat archives for spyder-ide/public

12th
Feb 2019
stonebig
@stonebig
Feb 12 18:30
hi all, I don't plan to do anything for Python-2.7 nor Windows7. but older Winpython versions (or betas) dated before may 2018 should not have the root problem, if MKL of 2018.0.3 is the problem. "Intel(R) MKL 2018 Update 3 ( May 2018) " found at https://software.intel.com/en-us/articles/intel-math-kernel-library-intel-mkl-2018-bug-fixes-list .
CAM Gerlach
@CAM-Gerlach
Feb 12 18:39
@stonebig Its MKL >= 2018.0.3 that happens to most often trigger the problem due to the implications on ABI compatibility with the third party software that most commonly triggered it, but it ultimately the root of the problem isn't in MKL at all. Due to its fundamental nature, it can happen with any MKL or OpenMP version that doesn't happen to match what is binary compatible with whatever DLLs any arbitrary program may have happened to throw into System32. Therefore, ideally, the fix should be implemented equally for all currently supported platforms if practicable, although realistically it may make sense to prioritize patching it for those on which users report it most frequently.
stonebig
@stonebig
Feb 12 18:45
it's a patch in python.exe itself ? If so, it's for Steve Dower
CAM Gerlach
@CAM-Gerlach
Feb 12 18:46
That's my understanding; for certain it doesn't anything to do with MKL, which is just an unfortunate victim of a much broader problem (DLL hell).
stonebig
@stonebig
Feb 12 18:52
submitted the problem to Steve Dower, the only one who can do something, if it's possible. using the "USA presidential phone" https://twitter.com/stonebigdotdot/status/1095394815402016768
CAM Gerlach
@CAM-Gerlach
Feb 12 18:52
Thanks @stonebig !
stonebig
@stonebig
Feb 12 18:55
maybe it should be posted on bugs.python.org, If you can welform the problem. I can't imagine the conda people not having posted it somewhere in bugs.python.org already
CAM Gerlach
@CAM-Gerlach
Feb 12 18:58
I'd have to ask Ray Donnelly, who'd probably be the best person to do it, and I'm not sure it'd get implemented since changing the DLL search order is serious business, a bit hacking and somewhat distribution-specific, but I can ask.
stonebig
@stonebig
Feb 12 18:59
zooba (Steve Dower) has already answered... apparently
CAM Gerlach
@CAM-Gerlach
Feb 12 18:59
?
if it's an old problem, maybe it's not such a frequent problem ?
CAM Gerlach
@CAM-Gerlach
Feb 12 19:05
It seems its becoming more of an issue now that modern mkl versions (and perhaps other libraries) are getting shipped/built with Python packages that are ABI-incompatible with the old versions that various software has dumped in System32. We've gotten dozens of reports in total over various channels in the past 6-12 months (since MKL 2018.0.3 came out), and none of the normal fixes apply for users and they have to muck around in their System32 to fix (a dangerous activity even for an experienced user, much less a newbie who could misread something and brick their system).
stonebig
@stonebig
Feb 12 19:07
I'm relying on cgohlke to fix every numeric bit, and never try otherwise anymore. For other bits, there is Steve Dower.
kevin chicaeme
@KChicaeme_twitter
Feb 12 23:20
good afternoon I continue with the following problem in the variable explorer, seeing some dataframes
imagen.png
imagen.png
CAM Gerlach
@CAM-Gerlach
Feb 12 23:52
@KChicaeme_twitter I've brought this up myself previously, but currently in order to view and edit special classes of objects in the Variable Explorer like Numpy arrays, Pandas dataframes and custom objects, you need the corresponding package installed in Spyder's environment as well as your working one. So in this case, you'd need to run conda install pandas in Spyder's environment to enable support for interacting with Numpy dataframes.
@ccordoba12 I know I've brought this up before, but is there any way to work around this limitation? Having to have the originating packages of any custom class objects, even those just being viewed as generic dicts, installed in Spyder's environment , defeats much of the purpose of allowing Spyder to be installed in a separate, isolated environment to begin with.