I think this could be one of the possible ways to address #71. In practice, the version requirements are defined on the libboost package, and based on these constraints, conda is expected to pick suitable boost-cpp and py-boost packages.
(I only tested the build on linux for python3, but I don't think these changes may be very specific to any build configuration).
I think this could be one of the possible ways to address #71. In practice, the version requirements are defined on the libboost package, and based on these constraints, conda is expected to pick suitable boost-cpp and py-boost packages.
(I only tested the build on linux for python3, but I don't think these changes may be very specific to any build configuration).