Convert arviz library to metapackage and global docs #2494
+677
−194,276
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prepare for 1.0 release with
arviz.previewbecoming the "main package".The main repo will then be a metapackage that installs the 3 arvizverse libraries
and exposes their functions through
arviz.xyz.Consequently, tests are only about aliases coming from the 3 other libraries.
I think we should keep some global docs here. I can look into making the docs of the
other 3 libraries be subprojects of the main one. That means they would get
python.arviz.org/projects/arviz-base/...as URLs, and we can look at doing somethingsimilar to what we do with PyMC to allow searching across all the different websites.
I have also found a couple minor issues with imports and targets for cross-references in the docs.
I will open PRs to the other repos soon.
📚 Documentation preview 📚: https://arviz--2494.org.readthedocs.build/en/2494/