Improve Action to Build and PyPi Release

[xRowe]

1. Update tox.ini pytest version to make test on python3.13 success
2. Update ci.yml to enable test on MacOS and python3.13
3. Substitute setup.cfg & setup.py with pyproject.toml, and remove tests folder in the build
4. remove some _version files. etc.
5. Update -> package version would be defined in file canmatrix.init attritbue version="x.y.z", Update everytime if RELEASE is wanted
6. Update ci.yml to enable when create Release in Github, it will automatically release to PyPI.
7. Update the README.md and convert it into README.rst, which would also presentation on PyPI

Demo on PyPI:
https://pypi.org/project/testpypi-canmatrix/

In my opinion, the tests file/scripts, should not occur in the release, so I remove it.
But the j1939.dbc, I have no idea to remove it, as it is necessary in j1939_decoder.py

Could you have a look if anything need improve?

Thanks,
Rowe

[coveralls]

Pull Request Test Coverage Report for Build 13388782039

Details

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+1.8%) to 54.518%

---

Totals
Change from base Build 13368031435:	1.8%
Covered Lines:	4453
Relevant Lines:	8168

---

💛 - Coveralls

[ebroecker]

Hi @xRowe

first of all thanks a for investigation your time in the CI issues!
This is definitely a thing which needs some work in canmatrix.

I don't understand everything perfectly, maybe you could help me a bit:

5. Update... : Does the release only happen if merged to master or does it also create a release and publish it, if canmatrix.__init__ is updated in other branch?
   Some times ago, when the "old CI" was working, a release was just created and uploaded every time I created a tag in master branch.
   What is the new workflow for doing a release? Change canmatrix.__init__ in master-branch and create a tag afterwards? How should this be done the correct way? Sorry, this question might seem stupid, but I have nearly no experience with the github ci...

6. Where have I to change, that it will publish in the correct PyPI, or does it work somehow magic if I enable github in PyPI?

And yes, j1939_decoder.py needs the dbc, while I don't know if anybody uses the j1939 decoder.

[xRowe]

5.Update... : Does the release only happen if merged to master or does it also create a release and publish it, if canmatrix.init is updated in other branch?
Some times ago, when the "old CI" was working, a release was just created and uploaded every time I created a tag in master branch.
What is the new workflow for doing a release? Change canmatrix.init in master-branch and create a tag afterwards? How should this be done the correct way? Sorry, this question might seem stupid, but I have nearly no experience with the github ci...
->
new workflow for doing a release I think you can do is,

• update the __version__ = "x.y.z" in file src/canmatrix/__init__.py
  https://github.com/xRowe/canmatrix/blob/aafff33af93835630820c4b0e0f1a274204d9112/src/canmatrix/__init__.py#L30
• merge everything you want into "master" branch, of course the change in step1), along with tests are all pass
• Then, you can "Draft a new release" at https://github.com/ebroecker/canmatrix/releases (This is the way I found)
• Create 'tag' and fill release note. etc......
• Click "Publish release" -> Only in this way, it can trigger "upload to pypi"

6. Where have I to change, that it will publish in the correct PyPI, or does it work somehow magic if I enable github in PyPI?
   ->
   Firstly, of course need your account in PyPI which organize canmatrix
   Then, need to Add a new pending publisher in https://pypi.org/manage/account/publishing/
   PyPI Project Name: canmatrix
   Owner: ebroecker
   Repository name: https://github.com/ebroecker/canmatrix
   Workflow name: ci.yml
   Click "Add", and think is ready.

After that, if release is triggered in the future, and builds is/are successful, then it will automatically upload to PyPI, and the version is equal to the one is set in file src/canmatrix/__init__.py attribute version

[ebroecker]

Hi @xRowe

thanks again, sounds good to me, I think understand now, gonna try this for the next release.
I'll merge this pr now.