openapi-python-client
cookiecutter
openapi-python-client | cookiecutter | |
---|---|---|
6 | 56 | |
1,075 | 21,618 | |
3.9% | 0.9% | |
9.0 | 8.7 | |
8 days ago | 5 days ago | |
Python | Python | |
MIT License | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
openapi-python-client
-
GraphQL is for Backend Engineers
On the backend, developers either need to manually document the entire API or rely on auto-generation tools that don’t fully meet their needs. Consumers face the same choice, write code by hand or workaround the bugs in their SDK generator (stated, lovingly, as the maintainer of an OpenAPI client generator). On top of this, these solutions result in inconsistent understandings of the API. Reproducing errors becomes time-consuming and frustrating, which feels like a battle instead of a collaboration. What we need is a shared language to describe how the API works—one that doesn’t add unnecessary layers of abstraction or manual work.
-
Microsoft Kiota: CLI for generating an API client to call OpenAPI-described API
Has anyone tried Kiota, specifically the Python support? How does it compare to https://github.com/openapi-generators/openapi-python-client ?
-
Python toolkits
I think we use these - https://github.com/openapi-generators/openapi-python-client
-
YAML: It's Time to Move On
Thanks for the link, but not necessarily.
How WSDL and the code generation around it worked, was that you'd have a specification of the web API (much like OpenAPI attempts to do), which you could feed into any number of code generators, to get output code which has no coupling to the actual generator at runtime, whereas Pyotr is geared more towards validation and goes into the opposite direction: https://pyotr.readthedocs.io/en/latest/client/
The best analogy that i can think of is how you can also do schema first application development - you do your SQL migrations (ideally in an automated way as well) and then just run a command locally to generate all of the data access classes and/or models for your database tables within your application. That way, you save your time for 80% of the boring and repetitive stuff while minimizing the risks of human error and inconsistencies, while nothing preventing you from altering the generated code if you have specific needs (outside of needing to make it non overrideable, for example, a child class of a generated class). Of course, there's no reason why this can't be applied to server code either - write the spec first and generate stubs for endpoints that you'll just fill out.
Similarly there shouldn't be a need for a special client to generate stubs for OpenAPI, the closest that Python in particular has for now is this https://github.com/openapi-generators/openapi-python-client
However, for some reason, model driven development never really took off, outside of niche frameworks, like JHipster: https://www.jhipster.tech/
Furthermore, for whatever reason formal specs for REST APIs also never really got popular and aren't regarded as the standard, which to me seems silly: every bit of client code that you write will need a specific version to work against, which should be formalized.
-
Replacing FastAPI with Rust: Part 2 - Research
Tallying up the results, we get 7/8 "MUST" requirements met. I think that Paperclip + actix-web seems like the most promising candidate. I'm really not opposed to writing the OpenAPI v3 construction myself as I've worked with the structure a fair bit in my openapi-python-client project (shameless plug).
-
Replacing FastAPI with Rust: Part 1 - Intro
Automatic documentation via OpenAPI, which lets you do things like generate Python code that knows how to talk to your API.
cookiecutter
-
Ask HN: How do you bootstrap your software projects?
Sometimes I use this to abstract boilerplate https://github.com/cookiecutter/cookiecutter
It can use a repo as a template.
It supports some interactive questions to choose options but mostly it is jinja templates.
Having libraries would be another option.
-
FastStream: Python's framework for Efficient Message Queue Handling
Install the cookiecutter package using the following command:
-
Template for Django Projects
Consider taking a look at cookiecutter to generate projects from templates. There is also cookiecutter-django. As for your environment variables you should have an example .env file containing all the environment variables required by your project (without setting them) that can be safely pushed into your repository for you and other developers to copy into the actual .env file that'll be used by your project (add this file to .gitignore)
- Rmarkdown/Github project organization question
-
Python Cookiecutter: Streamline Template Projects for Enhanced Developer Experience
The Python Cookiecutter library revolutionizes project development by offering streamlined approach to creating template projects and improving developer experience.
-
What do you use to generate Terraform/Grunt files at scale?
We use cookie cutter templates (the Python project, https://github.com/cookiecutter/cookiecutter ), we prompt for the module & version etc
-
A Python package that has a basic app setup inside it
Why not use cookiecutter or a similar tool designed for making these sorts of project templates?
-
Sub library with useful code
Is it common? I don't know. Is it useful? Absolutely. There is a tool called cookiecutter that allows you to define your own setup. For example, my cookiecutter setup for a python library is here. You can see what it's like by first installing the cookiecutter cli and then running
-
New tool: Souce code generator from a given template
Also cookiecutter.
-
Introducing Visual Cookiecutter: a web UI for instanciating cookiecutter templates
Visual Cookiecutter enhances the functionality of cookiecutter by offering unique features such as required fields, conditional input parameters, optional descriptions, and the ability to fix mistakes easily. This package seamlessly integrates with cookiecutter so that all existing templates work out-of-the-box.
What are some alternatives?
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
copier - Library and command-line utility for rendering projects templates.
starlark - Starlark Language
Jinja2 - A very fast and expressive template engine.
paperclip - WIP OpenAPI tooling for Rust. [Moved to: https://github.com/paperclip-rs/paperclip]
backstage - Backstage is an open platform for building developer portals
okapi - OpenAPI (AKA Swagger) document generation for Rust projects
try - Dead simple CLI tool to try Python packages - It's never been easier! :package:
warp - A super-easy, composable, web server framework for warp speeds.
bashplotlib - plotting in the terminal
yaml-reference-parser
qbatch