Search
158 results for “pawamoy”
-
#FastAPI now has proper API docs 🎉 They are built with #mkdocstrings and a #Griffe extension for PEP 727. The PEP was written by @tiangolo himself!
-
The PR to add API docs to #python-#markdown was merged 🎉 72 files changed, +2K/-1K loc, quite a PR! https://github.com/Python-Markdown/markdown/pull/1379
Too bad the docs deploy job failed 😅 Will update and add the link once the docs are up 🙂
Also, it means we'll be able to load Python-Markdown's inventory and cross-reference its API!
With #mkdocstrings:
-
The #Python handler of #mkdocstrings now supports rendering function signature overloads. It stacks them up vertically (see screenshots).
-
CW: Scary plushie
Got myself a plushie of the beast from Amnesia: The Bunker.
Waiting my Soma hoodie now 😤
-
Trying #Solid pods right now. Failing. Signed up at #Inrupt's #PodSpaces. Somehow can't use it to login into Liqid Chat, doesn't give me a pod URL. Tried signing up at inrupt.net instead. "Registration closed" once you sent the form... Got a pod at solidweb.org instead. "Unauthorized" when trying to log in with it. solidcommunity.net shows errors on its register page...
Finally managed to log into the PodPro app with Inrupt's PodSpaces.
I guess some apps aren't super well maintained?
-
PEP 751 is accepted, congratulations to @brettcannon and everyone else involved 🙂 🎉
https://discuss.python.org/t/pep-751-one-last-time/77293/150
-
I'm playing with #pyodide (https://pyodide.org), so that users can try out my Python packages directly into the docs pages! The editor is #ace (https://ace.c9.io/), and the output is highlighted with #highlightjs (https://highlightjs.org/). I'm trying to improve the look and feel but it's already amazing.
-
How do you generate JSON schemas of your dataclasses' **inputs**? Any third-party library (something else than stdlib's dataclasses) allowing one to do that?
For example, input type is `int | str`, but final/output type is always `int` (coerced). I want to document the input type, not the output type.
-
How do you generate JSON schemas of your dataclasses' **inputs**? Any third-party library (something else than stdlib's dataclasses) allowing one to do that?
For example, input type is `int | str`, but final/output type is always `int` (coerced). I want to document the input type, not the output type.
-
How do you generate JSON schemas of your dataclasses' **inputs**? Any third-party library (something else than stdlib's dataclasses) allowing one to do that?
For example, input type is `int | str`, but final/output type is always `int` (coerced). I want to document the input type, not the output type.
-
How do you generate JSON schemas of your dataclasses' **inputs**? Any third-party library (something else than stdlib's dataclasses) allowing one to do that?
For example, input type is `int | str`, but final/output type is always `int` (coerced). I want to document the input type, not the output type.
-
Also, use #Cappa 😛 Cappa leaves your functions/dataclasses (commands) intact.
-
Also, use #Cappa 😛 Cappa leaves your functions/dataclasses (commands) intact.
-
Also, use #Cappa 😛 Cappa leaves your functions/dataclasses (commands) intact.
-
Also, use #Cappa 😛 Cappa leaves your functions/dataclasses (commands) intact.
-
Rewriting an argparse-based CLI with #Cappa. It's much cleaner:
- less verbose
- better contained (single module instead of using submodules for subcommands)
- better typed (dataclasses!)
- as reusable, or more reusable in other CLIs (classes instead of functions that modify an argparse parser)
- much easier to use programmatically (no need to call `main` or build an `argparse.Namespace` manually)
- better documented
- better output (rich!) -
Rewriting an argparse-based CLI with #Cappa. It's much cleaner:
- less verbose
- better contained (single module instead of using submodules for subcommands)
- better typed (dataclasses!)
- as reusable, or more reusable in other CLIs (classes instead of functions that modify an argparse parser)
- much easier to use programmatically (no need to call `main` or build an `argparse.Namespace` manually)
- better documented
- better output (rich!) -
Rewriting an argparse-based CLI with #Cappa. It's much cleaner:
- less verbose
- better contained (single module instead of using submodules for subcommands)
- better typed (dataclasses!)
- as reusable, or more reusable in other CLIs (classes instead of functions that modify an argparse parser)
- much easier to use programmatically (no need to call `main` or build an `argparse.Namespace` manually)
- better documented
- better output (rich!) -
Rewriting an argparse-based CLI with #Cappa. It's much cleaner:
- less verbose
- better contained (single module instead of using submodules for subcommands)
- better typed (dataclasses!)
- as reusable, or more reusable in other CLIs (classes instead of functions that modify an argparse parser)
- much easier to use programmatically (no need to call `main` or build an `argparse.Namespace` manually)
- better documented
- better output (rich!) -
@dancardin I'm now recommending #Cappa in my docs: https://mkdocstrings.github.io/griffe/guide/users/recommendations/public-apis/#the-cli-is-api-too (just a quick mention at the end of the section) 😄
-
@dancardin I'm now recommending #Cappa in my docs: https://mkdocstrings.github.io/griffe/guide/users/recommendations/public-apis/#the-cli-is-api-too (just a quick mention at the end of the section) 😄
-
@dancardin I'm now recommending #Cappa in my docs: https://mkdocstrings.github.io/griffe/guide/users/recommendations/public-apis/#the-cli-is-api-too (just a quick mention at the end of the section) 😄
-
@dancardin I'm now recommending #Cappa in my docs: https://mkdocstrings.github.io/griffe/guide/users/recommendations/public-apis/#the-cli-is-api-too (just a quick mention at the end of the section) 😄
-
#Cappa is awesome. @dancardin does a fantastic job on this project.
Command descriptions can be written in Markdown and are rendered with #Rich, so code blocks are syntax highlighted, and you can even add links. Amazing CLI experience.
Look at this beauty:
-
#Cappa is awesome. @dancardin does a fantastic job on this project.
Command descriptions can be written in Markdown and are rendered with #Rich, so code blocks are syntax highlighted, and you can even add links. Amazing CLI experience.
Look at this beauty:
-
What a rabbit hole. Even though #Cappa uses #Rich internally, forcing colors with `FORCE_COLOR=1` did not work.
After a super painful investigation, turns out my #Python code imports a module from #Copier which uses `colorama.init()`.
Changing that to `colorama.just_fix_windows_console()` fixed it, but the output still had an extra reset sequence at the end.
Turns out Copier imports #Plumbum colors module, which registers a function to reset styles at exit.
Don't run things at import time!
-
What a rabbit hole. Even though #Cappa uses #Rich internally, forcing colors with `FORCE_COLOR=1` did not work.
After a super painful investigation, turns out my #Python code imports a module from #Copier which uses `colorama.init()`.
Changing that to `colorama.just_fix_windows_console()` fixed it, but the output still had an extra reset sequence at the end.
Turns out Copier imports #Plumbum colors module, which registers a function to reset styles at exit.
Don't run things at import time!
-
I started sponsoring @dancardin (@[email protected]?) for their great work on #Cappa, a super elegant declarative CLI argument parser for Python: https://github.com/DanCardin/cappa. It makes all the right choices, allowing users to build good, reusable CLIs for their libraries, with #Rich support!
-
I started sponsoring @dancardin (@[email protected]?) for their great work on #Cappa, a super elegant declarative CLI argument parser for Python: https://github.com/DanCardin/cappa. It makes all the right choices, allowing users to build good, reusable CLIs for their libraries, with #Rich support!
-
I started sponsoring @dancardin (@[email protected]?) for their great work on #Cappa, a super elegant declarative CLI argument parser for Python: https://github.com/DanCardin/cappa. It makes all the right choices, allowing users to build good, reusable CLIs for their libraries, with #Rich support!