Autogenerate `pixi.toml`
Description
pixi.toml isn't actually used for anything, so it's only for people who deliberately want to use pixi, but I did add a CI check to ensure that everything's consistent.
For squash-merging.
TODO: add more documentation to scripts/generate-pixi-toml.py.
Related Issue
- [ ] Closes #
- [ ] Related to #
Checklist
- [ ] Checked that the pre-commit linting/style checks pass
- [ ] Included tests that prove the fix is effective or that the new feature works
- [ ] Added necessary documentation (docstrings and/or example notebooks)
- [ ] If you are a pro: each commit corresponds to a relevant logical change
Type of change
- [ ] New feature / enhancement
- [ ] Bug fix
- [ ] Documentation
- [ ] Maintenance
- [ ] Other (please specify):
📚 Documentation preview 📚: https://pytensor--1542.org.readthedocs.build/en/1542/
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 81.90%. Comparing base (
7efd1c5) to head (e272f7c). Report is 4 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #1542 +/- ##
==========================================
+ Coverage 81.86% 81.90% +0.03%
==========================================
Files 230 230
Lines 52508 52506 -2
Branches 9339 9339
==========================================
+ Hits 42987 43006 +19
+ Misses 7089 7070 -19
+ Partials 2432 2430 -2
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
Do we really need to add 10k lines to the project?
The lockfile is indeed big. I think we should chip away at the dependencies.
The lockfile does bring a few nice advantages: zero solve time, and exact reproducibility (per platform)