Skip to content

Split installation dependencies per backend#188

Merged
jackvreeken merged 1 commit into
masterfrom
deps-split
Nov 6, 2019
Merged

Split installation dependencies per backend#188
jackvreeken merged 1 commit into
masterfrom
deps-split

Conversation

@jackvreeken
Copy link
Copy Markdown
Contributor

@jackvreeken jackvreeken commented Jul 30, 2019

  • Make sure to tag 0.5.x, as this is backwards incompatible. Others will need to expliticly specify the backends they use when relying on us now, e.g . "pymoca[casadi]" instead of just "pymoca".

@jackvreeken
Copy link
Copy Markdown
Contributor Author

@gitlyap Is this something you can get behind? I only need the CasADi backend, and do not like always dragging along the sympy and lxml dependencies that come with pymoca. For you with the CasADi backend, you might not need lxml and CasADi (and matplotlib/jupyterlab).

Instead of "pip install pymoca", you would then do "pip install pymoca[sympy]" (or "pip install pymoca[all]" if you want behaviour similar to what happens now). You can also list it as such as a dependency in a setup.py of another project, i.e. "pymoca[casadi] >= 0.4.4".

@jackvreeken jackvreeken merged commit d773745 into master Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant