Skip to content

Code quality and best practices  #294

Description

@soxofaan

A couple of notes and ideas on how to improve code quality and adopt best practices

  • start using black for code formatting
  • lot of interesting pointers in the "Hypermodern Python" blog series and the related cookiecutter template, for example
    • the furo for docs looks very nice compared to the default sphinx theme we currently use
    • pre-commit with some basic lint/flake8/isort checks
  • simplify the release procedure and automate it more (e.g. git tag based automated release)
  • switch to src layout
  • add a documentation page with code style recommendations, focused on openEO usage patterns.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions