Skip to content

[WIP] Monorepo placeholders#2

Draft
amaloney wants to merge 274 commits intomainfrom
issue1/monorepo
Draft

[WIP] Monorepo placeholders#2
amaloney wants to merge 274 commits intomainfrom
issue1/monorepo

Conversation

@amaloney
Copy link
Member

@amaloney amaloney commented Mar 19, 2025

resolves #1

OriolAbril and others added 30 commits July 6, 2023 01:12
@OriolAbril
set up docs
ad73933
@OriolAbril
prepare initial release
f846cd2
@OriolAbril
improve docs on sel utils
89ecf1b
@OriolAbril
add ci_kind rcparam
d51ea5f
@OriolAbril
refactor proposal
281d839 
for now, accessor and base/intervals are following the proposed refactor
together with the kde function in base/density. Everything else still
has to be updated
@OriolAbril
add stats.module rcparam
d1784fa
@OriolAbril
start and share arviz-plots repo
f354370
@OriolAbril
add numbified eti function
6e269e7
@OriolAbril
fix combined default
74b9e45
@OriolAbril
fix tests and extend intervals functionality
b3448b1
@OriolAbril
add more checks to pre-commit
bca8cbb
@OriolAbril
add badges to readme
8df8b4e
@OriolAbril
improve plot_posterior and add tests for it
d67df77
@OriolAbril
add minimal docstrings
9f06a17
@OriolAbril
add init to test folder
ceaac9b
@OriolAbril
update plot_posterior
b38fb67
@OriolAbril
add some docs
573ccda
@OriolAbril
add docs and implement some feedback
0d99b89
@OriolAbril
improve api docs
f6da01f
@OriolAbril
ignore mystnb warning
77e0999
@aloctavodia @OriolAbril
add plot_trace (#1)
92c7252 
* add trace plot

* use convert_to_datatree in tests

* fix linters

* Add to draft API docs

---------

Co-authored-by: Oriol Abril-Pla <oriol.abril.pla@gmail.com>
@aloctavodia
rename plot_posterior and small improvements
8517969
@aloctavodia
fix test
b2956a7
@OriolAbril
switch to ruff
6b58a88
@OriolAbril
fix external tests
449fecb
@aloctavodia
Merge pull request #19 from arviz-devs/distplot
37e9054 
rename plot_posterior to plot_dist and small improvements
@aloctavodia
rename source file
42ea3c9
@aloctavodia
Merge pull request #21 from arviz-devs/rpp
b4f6054 
rename source file
@aloctavodia
add style
27ecb4f
@aloctavodia
add styles
3709269
aloctavodia and others added 20 commits March 20, 2025 10:16
@aloctavodia
Update _version.py (#40)
904d240
@github-actions @aloctavodia
update changelog for v0.5.0 changes (#41)
c4cfec5 
This commit was created by changelog-from-release in 'Post-release' CI workflow

Co-authored-by: aloctavodia <aloctavodia@users.noreply.github.com>
@aloctavodia
cap tail at 20% (#79)
b7d2974
@aloctavodia
transform pit values into ETI coverage values (#80)
b41e2db
@aloctavodia
Add coverage argument to pit plots (#185)
0ae8fb7 
* add coverage argument to pit plots

* add coverage argument to pit plots

* rm nonexistent plot

* fix gallery
@aloctavodia
bump release (#81)
b59de3a
@github-actions @aloctavodia
update changelog for v0.5.0 changes (#82)
238b5ff 
This commit was created by changelog-from-release in 'Post-release' CI workflow

Co-authored-by: aloctavodia <aloctavodia@users.noreply.github.com>
@aloctavodia
bump release (#186)
10fabc8
@aloctavodia
after release changes (#83)
cf68262
@aloctavodia
after release changes (#188)
1dc4a31
@github-actions @aloctavodia
update changelog for v0.5.0 changes (#187)
a57425c 
This commit was created by changelog-from-release in 'Post-release' CI workflow

Co-authored-by: aloctavodia <aloctavodia@users.noreply.github.com>
@aloctavodia
add loo_pit (#84)
7fa5738
@aloctavodia
Add plot_loo_pit (#190)
bec7fd9 
* add plot_loo_pit

* Update loopitplot.py

* fix docstring
@aloctavodia
add randomized loo_pit (#85)
2fff2f9
@aloctavodia
clean pit functions (#191)
7fd2856 
* clean pit functions

* fix gallery names
@aloctavodia
Add Nested rhat (#87)
1f097d4 
* add nested r-hat

* small fix
@amaloney
Add arviz-base
6ada96f
@amaloney
Add arviz-plots
094030f
@amaloney
Add arviz-stats
3d2d52c
@amaloney
merge repos together
572affe
@aloctavodia aloctavodia moved this to In progress in Beta New ArviZ Apr 11, 2025
@aloctavodia
Copy link

aloctavodia commented Apr 22, 2025

Here, we are recommending the use of uv, but uv seems to be focused on pure Python dependencies, contrary to, for example, conda/mamba. For instance, it is recommended to install PyMC using conda. Can we recommend using Pixi instead? I understand pixi uses uv under the hood, but also plays well with the conda ecosystem.

@amaloney
Copy link
Member Author

amaloney commented Apr 23, 2025

uv seems to be focused on pure Python dependencies, contrary to, for example, conda/mamba

Correct. uv is a Python only package manager like pip, while conda/mamba allows you to install packages from other languages. pixi also allows installing packages from other languages using conda-forge.

Can we recommend using Pixi instead?

  • If this question is in reference to installing PyMC with pixi, then yes you can definitely switch to using pixi with PyMC.
  • If this question is about using pixi for ArviZ, then no because pixi does not currently have the concept of a "workspace", which is needed for the monorepo architecture.

pixi uses uv under the hood, but also plays well with the conda ecosystem.

This is also correct, but it is lacking some features we are using to create a workspace, which is why we are using uv instead. We could reach out to pixi to see how we can help move the workspace concept along. I see they have an unstable concept of multiple packages https://pixi.sh/latest/build/workspace/#lets-get-started, which I can experiment with here.

@aloctavodia
Copy link

aloctavodia commented Apr 24, 2025

Let me reframe my concerns, and sorry if I missed this the first time we talked about this. Is the uv restriction only for developers or also for users? If it is for the developer, that's fine with me.

@amaloney
Copy link
Member Author

amaloney commented Apr 24, 2025

For now uv is only for devs. Once the package is on pypi, a user can use any number of tools to install it, e.g. pip, poetry, pixi. Once it is on conda-forge, then a user can use conda, mamba, or pixi to install it.

@aloctavodia
Copy link

aloctavodia commented Apr 24, 2025

Thanks for clarifying.

@amaloney
Copy link
Member Author

amaloney commented Apr 24, 2025

These are valid questions that should be documented. I'll update the issue to ensure we capture things to do when documenting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@aloctavodia aloctavodia aloctavodia left review comments

Assignees

@amaloney amaloney

Labels

None yet

Projects

No open projects
ArviZ 1.0
Status: No status

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

create monorepo

8 participants

@amaloney @aloctavodia @OriolAbril @imperorrp @sethaxen @PiyushPanwarFST @The-Broken-Keyboard @suhaani-agarwal