build: use pixi instead of poetry#10
Merged
albop merged 19 commits intoEconForge:mainfrom Sep 1, 2025
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR gets rid of the previous awkward workflow where development is done using pixi and builds using poetry, and allows the
dyno.pylibrary to be used as a source dependency in other pixi projects such asjupyter_dynare.It also contains a couple of commits that add a
_repr_html_method to theRecursiveSolutionclass in order to visualize its moments and steady state. This method should be eventually added to most major classes in the library in order to improve integration with the Jupyter ecosystem.