Flask VS requests

I'd suggest Flask or some of the smaller projects in the Pallets ecosystem:

https://github.com/pallets/flask

#!/usr/bin/python # # https://flask.palletsprojects.com/en/3.0.x/installation/ # from flask import Flask, jsonify, request contacts = [ { "id": "1", "firstname": "Lorem", "lastname": "Ipsum", "email": "[email protected]", }, { "id": "2", "firstname": "Mauris", "lastname": "Quis", "email": "[email protected]", }, { "id": "3", "firstname": "Donec Purus", "lastname": "Purus", "email": "[email protected]", } ] app = Flask(__name__, static_url_path='', static_folder='public',) @app.route("/contact//save", methods=["PUT"]) def save_contact(id): data = request.json contacts[id - 1] = data return jsonify(contacts[id - 1]) @app.route("/contact/", methods=["GET"]) @app.route("/contact//edit", methods=["GET"]) def get_contact(id): return jsonify(contacts[id - 1]) @app.route('/') def root(): return app.send_static_file('index.html') if __name__ == '__main__': app.run(debug=True)

I was looking at all the big projects like numpy, pytorch, flask, etc.

Explore here.

I may use Flask-Admin initially to offload the "CRUD" operations to have an initial prototype fast but then drop it ASAP because I don't want to write a "flask-admin application" to fight against later on. If the application is mainly "CRUD", then Flask-Admin is suitable.

Now...

Would you do a breakdown/list of all the jobs you've done by sector/vertical and by function/role and by application functionality?

- [0]: https://flask.palletsprojects.com

- [1]: https://flask-admin.readthedocs.io/en/latest

- [2]: https://flask.palletsprojects.com/en/2.3.x/patterns/celery

- [3]: https://sentry.io

- [4]: https://posthog.com

- [5]: https://www.docker.com

In the lab to follow, we will be setting up an end-to-end DevOps workflow for a Flask microservice with GitHub Actions, using a self-managed custom runner for maximal control over the pipeline execution environment and automating deployments to a local Kubernetes cluster. Furthermore, we will construct separate pipelines for our "development" and "production" environments to further elaborate on the concepts of continuous deployment and delivery.

Flask Micro web Framework: You will use Flask to build a Flask web application.

In an earlier post I mentioned a bunch of Open Source web applications. Let's now focus on the ones written in Python using Flask the light-weight web framework.

For many years now, Requests has been frozen. Being left in a vegetative state and not evolving, this blocked millions of developers from using more advanced features.

- Ubiquitous “requests” library used in most docs examples, no async support https://github.com/psf/requests

Explore here.

It's Lukasa (his name is Cory, there's Łukasz in PSF though, but that's a different person). Looking at him, he made significant contributions to the requests repo: https://github.com/psf/requests/graphs/contributors

> I'd love to see the look on some of these people's faces when they find out that tool/software/whatever they use is actually using libcurl under the hood.

Python dependencies (does not include curl)

https://devguide.python.org/getting-started/setup-building/i...

The "requests" module in Python (does not use curl)

https://github.com/psf/requests

This part can be found in the README of the GitHub repository.

Looking around for similar errors I found this issue where they recommended trying to use a newer version of the urllib3 library.

but I appreciate the fact that there is an issue about it, it's acknowledged and .. unfixable, it would now break too many things https://github.com/psf/requests/issues/2002

The requests package has been the golden standard for package structure for as long as I can remember.