<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sphinx on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/sphinx/</link><description>Recent content in Sphinx on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 28 Jul 2026 07:00:00 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/sphinx/index.xml" rel="self" type="application/rss+xml"/><item><title>Meet APIdia: A New Approach to API Documentation Browsing</title><link>https://javapro-en.svenruppert.com/meet-apidia-a-new-approach-to-api-documentation-browsing/</link><pubDate>Tue, 28 Jul 2026 07:00:00 +0000</pubDate><guid>https://javapro-en.svenruppert.com/meet-apidia-a-new-approach-to-api-documentation-browsing/</guid><description>&lt;p&gt;When I became a researcher, my day-to-day programming moved from Java to scientific computing with Python. On this transition, a notable change was the character of the documentation. Java APIs were typically presented as structured systems, organized around packages and classes that could be browsed with relative ease. In contrast, much of the Python documentation I encountered, including the standard library and popular projects such as NumPy and SciPy, appeared primarily as a sequence of authored pages like a manual.&lt;/p&gt;</description></item></channel></rss>