arviz-devs/arviz

Conda forge packages for arvizverse

Open

#2498 opened on Dec 9, 2025

View on GitHub
 (16 comments) (0 reactions) (1 assignee)TeX (1,818 stars) (495 forks)batch import
DiscussionHelp Wanted

Description

The new modular structure with the 3 subpackages relies heavily on pip's bundles of optional dependencies. Conda doesn’t allow optional dependencies, but we can have extra packages to “compensate”. For example, matplotlib has matplotlib-base which has not backend and is recommended for downstreams to depend on and matplotlib which includes a recommended backend for users.

We currently have the following conda->pip equivalences

  • arviz-base -> arviz-base
  • arviz-stats -> arviz-stats[xarray]
  • arviz-plots -> arviz-plots

We definitely need to update the dependencies of the already existing arviz package on conda forge. However I am not completely sure to what.

We could also add:

  • arviz-stats-core -> arviz-stats
  • arviz -> arviz[matplotlib]?
  • arviz-plotly -> arviz[plotly] (most relevant for plotly because conda install arviz/arviz-plots plotly won’t work due to webcolors dependency missing)
  • arviz-bokeh -> arviz[bokeh]

Having more feedstocks isn't a huge overhead but it takes some resources on conda forge's side and we'll also have to review their recipes every time we make a release even if the review is short.

Contributor guide

Tech stack
python
Domain
devops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Python packagingconda forge basicsArviZ package structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate current conda forge arviz recipe to update dependencies. Determine which extra packages (e.g., arviz stats core, arviz plotly) to create as separate feedstocks. Check conda forge guidelines for optional dependency handling. Possibly open a PR to update the arviz feedstock first, then create new feedstocks if needed.