Search
158 results for “pawamoy”
-
mkdocstrings users, how would you feel if the Python handler started depending on Pydantic? The goal is to improve data validation (configuration options) as well as error reporting, and ease maintenance of JSON schemas (linting in IDEs like VSCode).
-
I added a few pages to #Griffe's docs: alternative projects, downstream projects, and built-in/official/third-party extensions.
Very cool projects mentioned in there! #Docspec, #pdoc, #papyri, #quartodoc, etc. And I discovered a few Griffe extensions in the process, it's awesome 🤩
- https://mkdocstrings.github.io/griffe/alternatives/
- https://mkdocstrings.github.io/griffe/downstream-projects/
- https://mkdocstrings.github.io/griffe/extensions/built-in/ -
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!
-
Damn, my #pkgx GitHub issue is on the orange front-page :rofl: Maybe one day I'll make it with one of my own projects instead 😂
-
#Cappa puts the finger on what I dislike about #Click: https://cappa.readthedocs.io/en/latest/comparison.html#why-not-click. I'll try Cappa right now in a new project.
I was also strongly tempted by #arguably (https://github.com/treykeown/arguably), but Cappa's use of `Annotated` instead of docstrings makes it super attractive given my recent work on supporting PEP 727 (from @tiangolo) with a #Griffe extension.
-
Should new warnings (logs or actual warnings) emitted given the same previous contents (user code/docs didn't change) be considered a breaking change?
-
We're starting to have a number of #Griffe extensions 🤩 They're all listed here: https://mkdocstrings.github.io/griffe/extensions/official/
-
We're starting to have a number of #Griffe extensions 🤩 They're all listed here: https://mkdocstrings.github.io/griffe/extensions/official/
-
We're starting to have a number of #Griffe extensions 🤩 They're all listed here: https://mkdocstrings.github.io/griffe/extensions/official/
-
We're starting to have a number of #Griffe extensions 🤩 They're all listed here: https://mkdocstrings.github.io/griffe/extensions/official/
-
We're starting to have a number of #Griffe extensions 🤩 They're all listed here: https://mkdocstrings.github.io/griffe/extensions/official/
-
I added a few pages to #Griffe's docs: alternative projects, downstream projects, and built-in/official/third-party extensions.
Very cool projects mentioned in there! #Docspec, #pdoc, #papyri, #quartodoc, etc. And I discovered a few Griffe extensions in the process, it's awesome 🤩
- https://mkdocstrings.github.io/griffe/alternatives/
- https://mkdocstrings.github.io/griffe/downstream-projects/
- https://mkdocstrings.github.io/griffe/extensions/built-in/ -
I added a few pages to #Griffe's docs: alternative projects, downstream projects, and built-in/official/third-party extensions.
Very cool projects mentioned in there! #Docspec, #pdoc, #papyri, #quartodoc, etc. And I discovered a few Griffe extensions in the process, it's awesome 🤩
- https://mkdocstrings.github.io/griffe/alternatives/
- https://mkdocstrings.github.io/griffe/downstream-projects/
- https://mkdocstrings.github.io/griffe/extensions/built-in/ -
I added a few pages to #Griffe's docs: alternative projects, downstream projects, and built-in/official/third-party extensions.
Very cool projects mentioned in there! #Docspec, #pdoc, #papyri, #quartodoc, etc. And I discovered a few Griffe extensions in the process, it's awesome 🤩
- https://mkdocstrings.github.io/griffe/alternatives/
- https://mkdocstrings.github.io/griffe/downstream-projects/
- https://mkdocstrings.github.io/griffe/extensions/built-in/ -
@benfulton @leahawasser I think most Python tools that measure cyclomatic complexity are based on or use McCabe, from @nedbat (https://pypi.org/project/mccabe/). #PyLint has it built-in, #Flake8 has plugins (McCabe is one), #Ruff probably has it built-in too.
-
Cross-posting from Twitter 😅
I'm working on adding a #codespell backend to my mkdocs-spellcheck plugin:
-
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) 😄
-
#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:
-
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!