# Dependency conflict and NumPy 2.0 support

**URL:** <https://discuss.bayesflow.org/t/dependency-conflict-and-numpy-2-0-support/209>\
**Category:** General\
**Created:** [November 6, 2025, 8:13pm UTC](https://discuss.bayesflow.org/t/dependency-conflict-and-numpy-2-0-support/209 "2025-11-06T20:13:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![freund](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@freund](https://discuss.bayesflow.org/u/freund)\
**Post date:** [November 6, 2025, 8:13pm UTC](https://discuss.bayesflow.org/t/dependency-conflict-and-numpy-2-0-support/209/1 "2025-11-06T20:13:49Z")

</div>

Hello,

I’m running into an installation conflict and wanted to ask about potential plans for `numpy >=2.0` support.

I have a project where I’d like to use both `bayesflow` and a recent version of another package, [`ssm-simulators`](https://github.com/lnccbrown/ssm-simulators). `Bayesflow` currently requires `numpy~=1.26` whereas current versions of `ssm-simulators` require `numpy>=2.0`. This prevents them from being installed in the same environment.

Are there any plans to update `bayesflow` to support `numpy>=2.0`?

Thanks for any information.

PS: Downgrading `ssms` is not an option for me unfortunately. So as a temporary work-around I’m attempting to run one of the packages with an unsupported version of numpy.

---

<div class="post-metadata">

**Author:** ![KLDivergence](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.bayesflow.org/kldivergence/32/15_2.png) [@KLDivergence](https://discuss.bayesflow.org/u/KLDivergence)\
**Post date:** [November 6, 2025, 8:43pm UTC](https://discuss.bayesflow.org/t/dependency-conflict-and-numpy-2-0-support/209/2 "2025-11-06T20:43:47Z")

</div>

You should not have any problems with `numpy > 2.0` on PyTorch / JAX backends. The requirement for `~1.26` will be removed in the next release.