{"version":"https:\/\/jsonfeed.org\/version\/1","title":"mathspp.com feed","home_page_url":"https:\/\/mathspp.com\/blog\/tags\/open-source","feed_url":"https:\/\/mathspp.com\/blog\/tags\/open-source.json","description":"Stay up-to-date with the articles on mathematics and programming that get published to mathspp.com.","author":{"name":"Rodrigo Gir\u00e3o Serr\u00e3o"},"items":[{"title":"TIL #135 \u2013 Build the Python documentation","date_published":"2025-10-26T14:44:00+01:00","id":"https:\/\/mathspp.com\/blog\/til\/build-the-python-documentation","url":"https:\/\/mathspp.com\/blog\/til\/build-the-python-documentation","content_html":"

Today I learned how to build the Python documentation to preview changes I wanted to make.<\/p>\n\n

If you're not on Windows, all it takes is to run make -C Doc venv htmllive<\/code> to build the Python documentation locally and to preview it.\nThis command will build the documentation, start a local server to browse the docs, and also watch for changes in the documentation source files to live-reload while you edit!<\/p>\n

I needed this because the Python 3.14 documentation for the module concurrent.interpreters<\/code> had a terrible-looking \u201cSee also\u201d callout with elements that were grossly misaligned:<\/p>\n

\"\u201cSee
This makes my want to cry.<\/figcaption><\/figure>\n

However, since I don't know rST, only Markdown, the issue wasn't obvious to me:<\/p>\n

.. seealso::\n\n   :class:`~concurrent.futures.InterpreterPoolExecutor`\n      combines threads with interpreters in a familiar interface.\n\n    .. XXX Add references to the upcoming HOWTO docs in the seealso block.\n\n   :ref:`isolating-extensions-howto`\n       how to update an extension module to support multiple interpreters\n\n   :pep:`554`\n\n   :pep:`734`\n\n   :pep:`684`<\/code><\/pre>\n
After some Googling, turns out the problem is the comment .. XXX Add references...<\/code>.\nSince it's indentend four spaces, it's being interpreted as a blockquote!\nThe fix was just deleting a single space from the left of .. XXX ...<\/code>.<\/p>\n
However, I did not stop there!\nI went above and beyond, capitalising the sentences and adding a full stop to the one that didn't have it!<\/p>\n
In the end, the \u201cSee also\u201d callout was looking better:<\/p>\n
\"\u201cSee
What a work of art.<\/figcaption><\/figure>","summary":"Today I learned how to build the Python documentation to preview changes I wanted to make.","date_modified":"2025-10-26T15:51:58+01:00","tags":["python","open source"],"image":"\/user\/pages\/02.blog\/04.til\/135.build-the-python-documentation\/thumbnail.webp"},{"title":"503 days working full-time on FOSS: lessons learned","date_published":"2024-04-01T00:00:00+02:00","id":"https:\/\/mathspp.com\/blog\/503-days-working-full-time-on-foss-lessons-learned","url":"https:\/\/mathspp.com\/blog\/503-days-working-full-time-on-foss-lessons-learned","content_html":"
This article shares some of the lessons I learned from working full-time on a FOSS project for 503 days.<\/p>\n\n
From the 14th of November of 2022 to the 31st of March of 2024 I worked full-time on a FOSS project.\nThis article is an account of some of the things that I learned during those 503 days.<\/p>\n
\n
I have much more time to devote to you<\/strong><\/em> now that I don't have this full-time position.\nIf you're looking for Python training, reach out to me<\/a>.\nI'll also be investing my time in this blog and in my books<\/a>.<\/p>\n<\/div>\n
I joined Textualize, the company behind the popular FOSS Python packages Rich<\/a> and Textual<\/a>, on the 14th of November of 2022.\nWhen I joined to work remotely from sunny Portugal, I joined Will<\/a> (the creator of Rich & Textual, and my boss), Darren<\/a>, and Dave<\/a>, all of whom worked together in Scotland.\nFor the first time in my professional life, I was the worst Python developer in the room1<\/a><\/sup>.\nThis means that my technical knowledge improved substantially over the course of these 503 days, namely in areas such as:<\/p>\n