Future improvements

[skearnes]

          > So maybe we should keep those deps in librdkit since they're still technically part of the C++ part that enables the python bindings in the rdkit package

The only problem is that they link to Python stuff, so I think they would better belong in rdkit because you only want them for Python usage, does that make sense? Not a blocker for now, but something to add to the list of improvements in the split (along with those header files we mentioned a few comments above). Feel free to merge whenever.

Originally posted by @jaimergp in https://github.com/conda-forge/rdkit-feedstock/issues/158#issuecomment-2243071415

[skearnes]

For the python stuff, I think we might need to rearrange the top-level build so we can build the python bindings as part of the rdkit package build instead?

[jaimergp]

From the same thread, I'd also highlight the need to improve:

• this bit with the dylib extension in rdkit-postgresql
• headers and cmake config files in librdkit

[skearnes]

From the same thread, I'd also highlight the need to improve:

• this bit with the dylib extension in rdkit-postgresql
• headers and cmake config files in librdkit

dylib fixed in #166