Search
158 results for “pawamoy”
-
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?
-
Kinda crazy to see #Griffe mentioned as inspiration for the design of #OpenAI's Agents SDK 🤯 Cool to see the SDK's API reference being documented with #mkdoctrings, too 🥰
-
Kinda crazy to see #Griffe mentioned as inspiration for the design of #OpenAI's Agents SDK 🤯 Cool to see the SDK's API reference being documented with #mkdoctrings, too 🥰
-
Kinda crazy to see #Griffe mentioned as inspiration for the design of #OpenAI's Agents SDK 🤯 Cool to see the SDK's API reference being documented with #mkdoctrings, too 🥰
-
Kinda crazy to see #Griffe mentioned as inspiration for the design of #OpenAI's Agents SDK 🤯 Cool to see the SDK's API reference being documented with #mkdoctrings, too 🥰
-
Kinda crazy to see #Griffe mentioned as inspiration for the design of #OpenAI's Agents SDK 🤯 Cool to see the SDK's API reference being documented with #mkdoctrings, too 🥰
-
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/ -
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.
-
@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.