Bring Python binding up to date

[Adda0]

Python binding was implemented for older C++ implementation of Mata. Since then, a lot has changed and Python binding needs to be brought up to date to the latest C++ implementation.

• [x] Convert setup.py to pyproject.toml.
• [x] Make function in Nfa and Afa namespaces a normal functions in module mata.{n, a}fa. This corresponds to how C++ Mata library is organized.
• [ ] Potentially create new examples in Jupyter notebooks.
• [ ] Add implementation for new Mata functions and update the current ones to reflect the interface in C++ library as much as possible.
• [ ] Create Delta as a Python object to allow calling nfa.delta.add(), etc. for operations on transitions; similar to C++ interface.
• [x] Add guide on how to work with Python binding and maintain it. We should create a document explaining how to work with and maintain Python binding in case all our Python binding developers (both of them!) are met with an unfortunate accident. The document should explain how to maintain the binding, extend the binding further, and where to look when something breaks and someone needs to fix the errors.
• [x] get rid of the ‘-std=c++20’ is valid for C++/ObjC++ but not for C warning message when compiling.
• [x] Divide Python binding into modules Python binding code becomes unmaintainable. We need to divide the code for Python binding into modules. Then we can call functions in the same manner as in C++ implementation, such as mata.nfa.concatenate(), etc.
• [x] Update example Jupyter notebooks.
• [x] Start automatically running the Jupyter notebook examples again with each build.

[Adda0]

We have decided that Python binding should play an important role in Mata library, and we should keep the binding up to date always.

[Adda0]

We need to prioritize for:

• Divide Python binding into modules,
• Update example Jupyter notebooks.

[tfiedor]

Can you elaborate, why this prioritization is needed now? I have all this in my todo and will soon work on the binding again, just need to know if there is some sudden need for these things.

[Adda0]

Can you elaborate ...

We decided to prioritize what needs to be done for TACAS 23.

[tfiedor]

I checked out the remark about warnings, since I believe, because of the building changes, they are now obsolete.

[kilohsakul]

I am thinking about changing the way we approach the python binding. Not sure we can really afford to have it as a top priority, there will not be so much spare manpower any more. After it is up to date with and ok in the current/tacas version of mata, we should talk about how to continue with it.