[BLOG] Add libsf_error_state: SciPy's first shared library

[steppi]

Sorry for accidentally targeting main with my first PR. Copied from before:

This is nearly done so I figured it was time to make a PR here. Irwin Zaid, who was involved in the work described has read this draft and given a thumbs up (after making a couple small suggestions).

I still need to add footnotes and write the conclusion section at the end, which currently has section header ##Reflections. It looks like I'll also need to go through and confirm the text styling bullet points.

Text styling

• The blog is written with plain language (where relevant).
• If there are headers, they use the proper header tags in order to do so (with only one level-one header).
• All links describe where they link to (for example, check the Quansight labs website).
• Any kind of styling that the author uses (for example, bold for emphasis) is consistent throughout the blog.

Non-text contents

• Blog post featured image is in PNG or JPEG format, not SVG.
• All content is represented as text (for example, images need alt text and videos need captions or descriptive transcripts).
• If there are emojis, there are not more than three in a row.
• Don't use flashing gifs or videos.
• If it were to be read as plain text, the blog still makes sense and no information is missing.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
labs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 24, 2025 5:27pm

[rgommers]

Great write-up Albert! I like the structure of the story.

[steppi]

Thanks @rgommers for all of the suggestions. Me not understanding why the inplace build works but not dev.py seems to be most in need of fixing. I'll look into understanding what's really going on. The empty brackets were places to remind me where to put the footnotes later. I should have mentioned that in my PR message. I've added footnotes now, and a conclusion section, and will go through and implement all of your suggestions.

[rgommers]

@steppi I fixed the RPATH handling description - please have a look.

[steppi]

Thanks @rgommers. I think I get it now. I left some suggestions which I hope did not change the meaning, trying to rewrite things using my own voice. Let me know if these look good.

[rgommers]

Thanks @steppi, those rewrites all looked good, so I merged them. Can you check the preview and see if you're happy with everything?

[steppi]

Thanks @steppi, those rewrites all looked good, so I merged them. Can you check the preview and see if you're happy with everything?

Thanks Ralf. I made a last minute fix to move a closing parenthesis to the correct position and updated the date of the post. It all looks good to me now.

[steppi]

Ha. Thanks Ralf

[rgommers]

Let's declare victory here:) Very nice post, thanks Albert!

[steppi]

@rgommers, is there anything I need to do to get this deployed on main? The instructions in the README say that labs blog-posts should be treated as code changes and follow the code-changes process which involves opening against develop, but I noticed just now that most (but not all) labs blog post pull requests are opened against main, and there is also a contradictory instruction I missed to open labs post pull requests against main. I guess the proper thing to do would be to cherry pick the commit over and open a new PR against main?

[rgommers]

Argh - yes indeed, this changed recently and I believe the instructions are outdated. Can you open a new PR to sync the changes to main? And a separate one to fix the instructions to prevent more people from being confused?