Consider poetry for dependency and package management

[euronion]

See if we want to use poetry for dependency management, package deployment to package repositories and project scaffolding.

Detailed Description

"Poetry is a tool for dependency management and packaging in Python. It allows you to declare the libraries your project depends on and it will manage (install/update) them for you." (https://python-poetry.org/docs/)

We could use poetry to recreate the atlite project scaffolding and/or manage the dependencies for the different package repositories like pypi and conda-forge and use poetry for deploying new atlite versions to these repositories.

Poetry consolidates most information which is currently redundantly specified and spread across files into a pyproject.toml file.

Context

Issues as in #143 caused by inconsistencies in maintaining the dependency files for different package repositories will arguably continue to arise as long as we have dependencies manually duplicated for different installation methods.

Possible Implementation

/

[FabianHofmann]

definitively agree!

[coroa]

Poetry does not support combining multiple projects in a manner similar to pip install -e . at the same time as far as i am aware (ie. python-poetry/poetry#34). Ie. you could not use a development version of atlite with a development version of pypsa-eur easily (or at least i don't know how to). Maybe the PR python-poetry/poetry-core#182 solves that, but i have not investigated that.

Also note that we will always have duplication in conda definitions and the more low-level python packaging.

[FabianHofmann]

closing this as we (until now) run smoothly with the GH packaging workflow