Make fully Bayesian imports lazy (#5148) by sdaulton · Pull Request #5148 · facebook/Ax

sdaulton · 2026-04-06T20:03:43Z

Summary:

import botorch eagerly loaded Pyro via two import paths:

botorch.fit → from pyro.infer.mcmc import MCMC, NUTS
botorch.models.__init__ → fully_bayesian.py → Pyro imports

This diff makes fully Bayesian imports lazy so that import botorch no longer
eagerly loads Pyro. The imports are deferred until fit_fully_bayesian_model_nuts
is called or SaasFullyBayesianSingleTaskGP/SaasFullyBayesianMultiTaskGP are
accessed from botorch.models.

Reviewed By: saitcakmak

Differential Revision: D99687047

meta-codesync · 2026-04-06T20:03:51Z

@sdaulton has exported this pull request. If you are a Meta employee, you can view the originating Diff in D99687047.

Summary: X-link: meta-pytorch/botorch#3265 `import botorch` eagerly loaded Pyro via two import paths: 1. `botorch.fit` → `from pyro.infer.mcmc import MCMC, NUTS` 2. `botorch.models.__init__` → `fully_bayesian.py` → Pyro imports This diff makes fully Bayesian imports lazy so that `import botorch` no longer eagerly loads Pyro. The imports are deferred until `fit_fully_bayesian_model_nuts` is called or `SaasFullyBayesianSingleTaskGP`/`SaasFullyBayesianMultiTaskGP` are accessed from `botorch.models`. Differential Revision: D99687047

Summary: X-link: facebook/Ax#5148 `import botorch` eagerly loaded Pyro via two import paths: 1. `botorch.fit` → `from pyro.infer.mcmc import MCMC, NUTS` 2. `botorch.models.__init__` → `fully_bayesian.py` → Pyro imports This diff makes fully Bayesian imports lazy so that `import botorch` no longer eagerly loads Pyro. The imports are deferred until `fit_fully_bayesian_model_nuts` is called or `SaasFullyBayesianSingleTaskGP`/`SaasFullyBayesianMultiTaskGP` are accessed from `botorch.models`. Reviewed By: saitcakmak Differential Revision: D99687047

Summary: X-link: meta-pytorch/botorch#3265 `import botorch` eagerly loaded Pyro via two import paths: 1. `botorch.fit` → `from pyro.infer.mcmc import MCMC, NUTS` 2. `botorch.models.__init__` → `fully_bayesian.py` → Pyro imports This diff makes fully Bayesian imports lazy so that `import botorch` no longer eagerly loads Pyro. The imports are deferred until `fit_fully_bayesian_model_nuts` is called or `SaasFullyBayesianSingleTaskGP`/`SaasFullyBayesianMultiTaskGP` are accessed from `botorch.models`. Reviewed By: saitcakmak Differential Revision: D99687047

Summary: Pull Request resolved: facebook#5148 X-link: meta-pytorch/botorch#3265 `import botorch` eagerly loaded Pyro via two import paths: 1. `botorch.fit` → `from pyro.infer.mcmc import MCMC, NUTS` 2. `botorch.models.__init__` → `fully_bayesian.py` → Pyro imports This diff makes fully Bayesian imports lazy so that `import botorch` no longer eagerly loads Pyro. The imports are deferred until `fit_fully_bayesian_model_nuts` is called or `SaasFullyBayesianSingleTaskGP`/`SaasFullyBayesianMultiTaskGP` are accessed from `botorch.models`. Reviewed By: saitcakmak Differential Revision: D99687047

Summary: X-link: facebook/Ax#5148 Pull Request resolved: meta-pytorch#3265 `import botorch` eagerly loaded Pyro via two import paths: 1. `botorch.fit` → `from pyro.infer.mcmc import MCMC, NUTS` 2. `botorch.models.__init__` → `fully_bayesian.py` → Pyro imports This diff makes fully Bayesian imports lazy so that `import botorch` no longer eagerly loads Pyro. The imports are deferred until `fit_fully_bayesian_model_nuts` is called or `SaasFullyBayesianSingleTaskGP`/`SaasFullyBayesianMultiTaskGP` are accessed from `botorch.models`. Reviewed By: saitcakmak Differential Revision: D99687047