Billy K. Poon

I switched the Python to the one in `python.app` and added your wx test to the conda-forge recipe so the February 2022 (2022.2) release should work.

Yeah, the `python.app` package was updated to use symbolic links and the path is being resolved to the actual file instead of keeping the symbolic link during the dispatcher generation....

I've been looking into using conda for replacing our dependencies to address these compatibility issues. There is some preliminary work in the conda_build repository (https://github.com/cctbx/conda_build). Dependencies from conda should be...

No, we are not using ```conda``` for development or releases. We still use ```bootstrap.py base``` in our nightly builds. The ```conda_build``` repository is all preliminary work. There are still missing...

I can build a new build that adds the constraint. But we don't have to remove the old one. I'm trying to determine the underlying issue. https://github.com/conda-forge/cctbx-base-feedstock/pull/26

The new build that does not update to numpy 1.21 should be available. You may need to wait for the CDN to update for the package to be widely available.

We have seen segmentation faults with `numpy` before. It should be related to an initialization. Not everything that uses `numpy` causes a segmentation fault. I will narrow down which additional...

Have not had time to took further into this yet.

Great! I was not able to reproduce Derek's crash, but I was able to find another simple way of causing the segfault. There is also an earlier discussion here. https://github.com/epics-base/pvaPy/issues/63

Yeah, I've been following the discussion. But it looks like there should still be an update to Boost.Python. Thanks for getting the ball rolling! I should be able to add...