If you've got anything running on Google's Custom Search JSON API, it's on a clock. Google closed it to new customers and their overview page says it's gone on January 1, 2027.

Easy to miss in the docs: one call returns 10 results and a query tops out at 100. So pulling the top 100 for a single keyword is 10 billable calls.

For checking your own site's rankings there's an easier path anyway. The Search Console API hands you query, page, country and device rows, up to 25,000 per request, and it's all within Google's rules.

Anyone already moved off Custom Search? What did you switch to?

@mgorny@treehouse.systems:

After seeing yet another dozen packages lose keywords on Gentoo because of a single key dependency switching to uv-build, I would like to plea on behalf of Gentoo users: please don’t use uv-build as a build backend.

Just to be clear, this is not about uv itself or any other Astral tools; these are good tools with a nice and responsive upstream. The uv-build backend is one thing we have to disagree on. I’m not saying it’s bad; I’m saying that its benefits don’t outweigh the drawbacks.

A hard exercise to help build the right mental model for Python data.

• Solution: https://memory-graph.com/#codeurl=https%3A%2F%2Fraw.githubusercontent.com%2Fbterwijn%2Fmemory_graph_videos%2Frefs%2Fheads%2Fmain%2Fexercises%2Fexercise26.py&play=
• Explanation: https://github.com/bterwijn/memory_graph?tab=readme-ov-file#python-data-model

The “Solution” link visualizes execution and reveals what’s actually happening using 𝗺𝗲𝗺𝗼𝗿𝘆_𝗴𝗿𝗮𝗽𝗵: https://github.com/bterwijn/memory_graph

geteilt von: https://programming.dev/post/56750254

geteilt von: https://programming.dev/post/56750248

Checkout the release notes: https://ekxide.io/blog/iceoryx2-0.10-release/

Git: https://github.com/eclipse-iceoryx/iceoryx2

iceoryx2 book: https://ekxide.github.io/iceoryx2-book/main/

https://ingwerperium.codeberg.page/ingwerperium/pythonprojekt_de.html