Merge of pep_561_mypy to dev

Add support for PEP 561 (mypy import recognition) in the PyPi package.

added 1 commit

• 9eaf56c1 - [enh] #96 (closed) add manual release_test job to upload on test.pypi.org

Compare with previous version

added 1 commit

• ae588a0d - [enh] #96 (closed) fix gitlab-ci errors adding make commands for build and deploy

Compare with previous version

added 1 commit

• 5cb495e4 - [enh] #96 (closed) do not echo commands with password in MakeFile

Compare with previous version

added 1 commit

• a779e29f - [enh] #96 (closed) new gitlab-ci secret env var for test.pypi.org deploy

Compare with previous version

added 1 commit

• f3766039 - [fix] #96 (closed) fix gitlab-ci env var from settings is empty

Compare with previous version

changed milestone to %0.55.x

added 11 commits

• f3766039...4057ce93 - 4 commits from branch dev
• fc83b965 - [enh] #96 (closed) support PEP 561 for duniterpy type hints to be recognized by mypy when imported
• dac9ac4e - [enh] #96 (closed) add manual release_test job to upload on test.pypi.org
• a12ce5bc - [enh] #96 (closed) fix gitlab-ci errors adding make commands for build and deploy
• b42ff020 - [enh] #96 (closed) do not echo commands with password in MakeFile
• ae76e995 - [enh] #96 (closed) new gitlab-ci secret env var for test.pypi.org deploy
• b7863f2f - [fix] #96 (closed) fix gitlab-ci env var from settings is empty
• 1c19ff01 - [enh] #96 (closed) add install from test.pypi.org command in README

Compare with previous version

@moul, branch ready for review and merge !

The title of the MR does not represent what is the main topic of it.

For next time, please try to split changes into different MR.

For instance, one for PEP 561 and the other for the CI/CD enhancement (PyPI test).

I would rather use publish rather than deploy because we are publishing/releasing a new release of a library. We are not deploying a new version of a website on the server. So, the requirements, the Makefile and the doc, should be updated.

As maintainer of this project, give me the permission to not change the deploy word as it is really a deploy operation (as the D in CD, there is no P...).

I take your remarks as a validation for this MR and will rebase it on dev this week-end.

Next time I will not give you all my commits to review, only those that are at risk for the applications using duniterpy, so it will allow me to have more freedom shaping this project as I see it.

I will take in charge this release. I will let you know before I deploy, for you to be able to valid the release and alert me on any missing things.

That’s all right with deploy. publish was a proposition.

closed