russellballestrini/russell.ballestrini.net
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

credit botoform as nested-lookup origin, fan out to VPC & boto3 posts

Browse source
This commit is contained in:
russell@unturf.com 2026-02-27 17:54:37 -05:00
parent 5a358a9e88
commit 941bb27089
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
content/2026-02-27-a-love-story-about-jason.rst
View file

@ -34,7 +34,7 @@ I started seeing curly braces when I closed my eyes.
:align: center
:width: 400px
So I did what any rational person would do. I `wrote a library </dealing-with-pagination-in-python/>`_. I ripped ``nested_lookup()`` out of a paginated AWS ElastiCache nightmare & published it to `PyPI <https://pypi.org/project/nested-lookup/>`_. Public domain. Now nobody has to type ``response["data"]["data"]["results"][0]["data"]`` ever again. You just say ``nested_lookup("data", response)`` & it hands you every match from every depth. That frustration became a `real tool <https://git.unturf.com/python/nested-lookup>`_ that strangers install with ``pip``.
So I did what any rational person would do. I `wrote a library </dealing-with-pagination-in-python/>`_. While growing `Botoform <https://botoform.com>`_ to `manage AWS VPCs </output-all-instance-identifiers-of-an-aws-vpc-to-json/>`_ & `wrangle Boto3 responses </boto3-get-main-route-table/>`_, I kept hitting nested JSON walls. I ripped ``nested_lookup()`` out of that work & published it to `PyPI <https://pypi.org/project/nested-lookup/>`_. Public domain. Now nobody has to type ``response["data"]["data"]["results"][0]["data"]`` ever again. You just say ``nested_lookup("data", response)`` & it hands you every match from every depth. That frustration became a `real tool <https://git.unturf.com/python/nested-lookup>`_ that strangers install with ``pip``.
Love makes you grow things.