Search
158 results for “pawamoy”
-
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!
-
#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.
-
#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.
-
So cool to stumble on an episode of @pythonbytes where they talk about my tool Yore ☺️
https://www.youtube.com/live/HCRfjkbSbmE?si=Ydiuz_vxxHX5Cih6
https://github.com/pawamoy/yore
Yore supports marking legacy code for Python versions but also for the current project version. I plan to support dependencies versions too (and more ecosystems, like Rust).
-
Presenting #Yore again, because it's a nice little tool for library maintainers:
- mark legacy code with comments: `# YORE: EOL 3.9: Remove line`
- check periodically: `yore check`
- see applied diff (dry-run): `yore diff`
- actually fix comments: `yore fix` -
#MkDocs got a $50 contribution on #OpenCollective recently. The person who made the contribution used a gift card from #Redocly. Anybody has information on these gift cards? I'm very curious 🙂
-
#MkDocs got a $50 contribution on #OpenCollective recently. The person who made the contribution used a gift card from #Redocly. Anybody has information on these gift cards? I'm very curious 🙂
-
#MkDocs got a $50 contribution on #OpenCollective recently. The person who made the contribution used a gift card from #Redocly. Anybody has information on these gift cards? I'm very curious 🙂
-
#MkDocs got a $50 contribution on #OpenCollective recently. The person who made the contribution used a gift card from #Redocly. Anybody has information on these gift cards? I'm very curious 🙂
-
#MkDocs got a $50 contribution on #OpenCollective recently. The person who made the contribution used a gift card from #Redocly. Anybody has information on these gift cards? I'm very curious 🙂
-
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?
-
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?
-
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?
-
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?
-
I think #Griffe is ready for v1. Just one more v0 release to communicate one last deprecation.
-
I'm adding tests to #Griffe, that use Griffe to check if:
- all public objects are exposed in the top-level init module
- all public objects are added to the API docs (HTML), and therefore if they are added to the objects inventory (#Sphinx-like objects.inv file)
- if no other object is added to the inventory (no private objects)Thanks to these tests I made sure not to forget *anything* while rewriting Griffe's docs!
-
I'm experimenting with moving all my code into a private package, and exposing every public object in the top-level init module of a sibling public package:
- _griffe has all the internal API
- griffe exposes public objectsI added a test to my tests file that loads the internal #API (using #Griffe of course 😂) and checks that every "public" name in the internal API is exposed in the public package. Impossible to miss some, and that forces me to privatize the rest.
-
Working towards a v1.0 for #Griffe. I will enjoy removing all the legacy code used for backward compatibility 😛
We're not there yet. See the milestone: https://github.com/mkdocstrings/griffe/milestone/1
-
It's good to be challenged by users.
I was reluctant to add support in #Griffe for some conventions used in the #Python ecosystem to mark objects as "exported".
To make proper arguments, I had to take a good, serious look at my codebase again. By doing so, I actually identified issues and clear improvements, that once fixed/refactored would allow Griffe to easily support these conventions in a way that makes complete sense 👍
https://github.com/mkdocstrings/python/issues/39#issuecomment-2137083119
-
Quite the feature in #Griffe: the ability to force using dynamic analysis to extract data from #Python packages. Previously it would use static analysis by default and only fallback to dynamic analysis for built-in/compiled modules. Now you can use dynamic analysis for modules with sources available too 🙂
This wasn't an easy change as I thought, but I'm happy how the code evolved.
I've just released v0.45.0. Crossed-fingers for no regressions 🤞 (tests added, but, you know, can't ever be sure)
-
Thanks @orsinium. Until now I was fighting this (trying to find out the true parent module), but seeing how inconsistent this is, I give up and will just use what Python gives me.
To give more context: I'm trying to improve the code in #Griffe that inspects object trees (dynamic analysis). To know whether an object should be added to the currently inspected module as a member or as an alias pointing to somewhere else, I have to check where the object originates from.
https://github.com/mkdocstrings/griffe/commit/d1696b03a67560a997176d42d07b32395cf723d7
-
I have published a "best practices" document in #Griffe's docs:
https://mkdocstrings.github.io/griffe/best_practices/
It says:
- avoid member-submodule name shadowing (the issue described above ☝️)
- avoid wildcard imports
- prefer canonical imports (we recommend @15r10nk's canonical-import tool!)These recommendations are given from a "static analysis" and "public API" point of view.
I'll gradually add more of these 🙂
-
#Python devs, do you often have a submodule and a member with the same name?
For example:
- pkg/__init__.py declares `thing = 1`
- pkg also has a `thing.py` submodule#Griffe does not support that and will ignore the member in such cases, giving priority to the submodule. This limitation has been reported multiple times, and I wanted to fix it, but after having worked on it a bit, I'm quite convinced I shouldn't, and instead should say it's bad practice.
https://github.com/mkdocstrings/griffe/issues/124#issuecomment-1981072243
-
Next version of #Griffe will bring improved support for dataclasses. They are actually a PITA to handle statically 😵 200 LoC + 160 LoC for tests.
-
Yesterday I released two new #Insiders features, for #Griffe this time: two different output formats for the `check` command. You can now output in Markdown, useful for changelogs for example, and with GitHub Actions' "annotations" format, which are picked up by GitHub and displayed in the Checks tab and the Files Changed tab.
-
I started using pysource-codegen (https://github.com/15r10nk/pysource-codegen) to generate arbitrary but valid Python code to fuzz #Griffe. Great tool!
-
Also, I just realized that the `@typing.deprecated` extension for #Griffe (https://mkdocstrings.github.io/griffe-typing-deprecated/) was not made available to sponsors, so I added it to the insiders team too.