Conversation
|
I'm going to convert the branch of this PR to a PR against the mu-python-template on mu-semtech as it should be picked up there instead. I second @nvdk 's observation on the error handler. Ideally the template can be kept backwards compatible. We will likely make a feature-branch first which we will be able to extend with features which are now available in the Ruby and JavaScript templates. With the feature branch we should be unblocked. |
chore: update documentation feat: use uv package manager
|
@madnificent resolved that, also updated docs, introduced uv for dependency management (this is getting more and more traction and a lot faster) and was suggested by Peter in the advisory board. Especially, have a look at the bottom section of the README for some considerations and how they were handled in the template. |
…d expand minimally with some much needed compilers
|
@madnificent for testing I tried to convert the geocoding service to this image and ran into an issue with the python depedency installation because of missing system components (in this case g++) but I could immediately think of over 20 packages which depend on specific C/C++ libraries as they essentially provide wrappers. I added compilers to the template, but also added an option to include a build.sh which can be used to install system dependencies. |
Modernization of the template based on FastAPI and a more recent python version.