Feature/md 7041 publish python package

[marns93]

Added possibility to publish Python package to PyPI, see #32.

There is another PR to add the credentials: https://github.com/moneymeets/moneymeets-pulumi/pull/483, which I already applied.

We agreed on the following versioning schema:
locally: 1.1+SNAPSHOT
published: 1.0.202310461046+gabcde

The workflow can be tested by updating the branch from master to feature/MD-7041-publish-python-package in publish.yml.
Furthermore, there is a to-do item in pyproject.toml. @catcombo Please clarify and update this.

[catcombo]

I've updated classifiers according to the list of classifiers. I also preselected MIT license. We can discuss it in the IT daily if we want to choose another one.

[zyv]

I thinks MIT is the best for us. Thank you!

[catcombo]

I've tested building package locally and haven't found any problems with the package content or with the build process.

[marns93]

/rebase

[catcombo]

@felix11h Do you need more time to review this PR or can I merge it?

[felix11h]

Thank you for waiting for my review, @catcombo. I have approved the changes, there's nothing I see that would speak against merging as is.

I did leave some additional comments, which are in part for my own understanding. Maybe this is still something we can think and potentially update or change in a second step.

[felix11h]

Suggested change

	description = "YouTrack SDK"
	description = "YouTrack API SDK"

To make it consistent with the description of the GitHub repository?

[catcombo]

I'm not sure that YouTrack API SDK is the correct description. For example, boto3 is just AWS SDK for Python, not AWS API SDK. So maybe we should update repository description instead of package description.

[catcombo]

There are 2 problems:

1. Publishing failed because PyPI server doesn't support local versions (+git-hash). We'll discuss the solution to this in the ticket or in the daily.
2. I noticed that the publish workflow started in parallel with the CI workflow. Is it possible to start publishing only after CI has been successfully completed?

[marns93]

There are 2 problems:

1. Publishing failed because PyPI server doesn't support local versions (+git-hash). We'll discuss the solution to this in the ticket or in the daily.

:( Okay, let's discuss it again.

2. I noticed that the publish workflow started in parallel with the CI workflow. Is it possible to start publishing only after CI has been successfully completed?

We discussed this and the point from @felix11h was that CI workflow will be successful in feature branches, otherwise we can't merge to master. So it is okay to run in parallel. Otherwise, we could use the way with a composite action and add a condition, or we can check the trigger types.

[catcombo]

We discussed this and the point from @felix11h was that CI workflow will be successful in feature branches, otherwise we can't merge to master. So it is okay to run in parallel. Otherwise, we could use the way with a composite action and add a condition, or we can check the trigger types.

Thanks for the explanation. This makes sense.

[catcombo]

:( Okay, let's discuss it again.

We've decided in the IT daily to remove local version and deploy a package.