You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the current behavior?
We have currently made some choices regarding the software development tools utilized across the packages found in DESDEO. Some of these choices might require updating to a tool better suited given our needs.
Describe the solution you'd like
Based on our earlier discussion, we have the following tools on the table:
Package and project manager: poetry (same as before)
Formatter: black, but move to ruff once it is stable (previously black)
Linter: ruff (was pylint? previously)
Testing: pytest (same as before)
Python version: 3.12 and update as soon as possible
What is the motivation/use case for changing the behavior?
Since we are rethinking the structure of the project (see [IDEA] New project structure for DESDEO #73 ), it is a good time to rethink the software development tools we intend to use so that we may choose the tools that best suit our needs.
Describe alternatives you've considered
Especially to linters and formatters, there are many alternatives. ruff seems a good candidate because it is very fast and therefore does not slow down the development process due to, e.g., excess processing times. The discussion about moving to MkDocs from Sphinx is found in another issue ([IDEA] Documentation tool and style #72 ). There really are not better alternatives to poetry right now, and for testing, which will consist mostly of unit tests, pytest is an industry standard. With the Python version, we should update it as frequently as possible.
What is the current behavior?
We have currently made some choices regarding the software development tools utilized across the packages found in DESDEO. Some of these choices might require updating to a tool better suited given our needs.
Describe the solution you'd like
Based on our earlier discussion, we have the following tools on the table:
What is the motivation/use case for changing the behavior?
Since we are rethinking the structure of the project (see [IDEA] New project structure for DESDEO #73 ), it is a good time to rethink the software development tools we intend to use so that we may choose the tools that best suit our needs.
Describe alternatives you've considered
Especially to linters and formatters, there are many alternatives. ruff seems a good candidate because it is very fast and therefore does not slow down the development process due to, e.g., excess processing times. The discussion about moving to MkDocs from Sphinx is found in another issue ([IDEA] Documentation tool and style #72 ). There really are not better alternatives to poetry right now, and for testing, which will consist mostly of unit tests, pytest is an industry standard. With the Python version, we should update it as frequently as possible.
Additional context
The text was updated successfully, but these errors were encountered: