It looks like this is actually due to a problem with the conda boost
builds, not an RDKit problem, but I've replaced the binary anyway.
As of right now, the version of the py-boost library available through the
default conda channel for windows and python 3.5 (py-boost:
1.65.1-py35h6538335_4) does not work. Because this is on the default conda
channel, it is very likely that this is what you will get if you try to
install the RDKit. To avoid the problem, you can install the py-boost build
from the anaconda channel with:
conda install -c anaconda py-boost
If you follow this with:
conda install -c rdkit rdkit
the installation should work.
Best,
-greg
On Fri, Apr 27, 2018 at 10:13 AM Greg Landrum <greg.land...@gmail.com>
wrote:
> Dear all,
>
> There was a problem with the RDKit 2018.03.1 conda package for python 3.5
> on Windows. I've removed that package and will try to get a new one up
> later today.
>
> For those who care: somehow one of the dependencies that was installed
> introduced a boost.python DLL that was looking for python3.6, despite this
> being a python3.5 build. I'm working on tracking down what caused that
> (it's not a problem on linux) and fixing the conda build script.
>
> -greg
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Rdkit-discuss mailing list
Rdkit-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rdkit-discuss