Add Python memory management post

[d33bs]

This PR adds a new blog post covering Python memory management and troubleshooting. The work is inspired from content initially developed in CU-DBMI/demo-python-memory-reference-accounting#1 , which is a test-driven investigation of Python memory. My hope here is to share information on the same topics while allowing for greater flexibility to explore memory implications within CU-DBMI/demo-python-memory-reference-accounting.

As part of this work I also added a "tip-of-the-month" includes block to adjust to newsletter wording and a less frequent post cadence. We could also drop the nomenclature here as well to provide more flexibility.

Thank you in advance for any feedback and input you may have!

CC @chrisroederucdenver

Relates to work in cytomining/CytoTable#75

[netlify[bot]]

✅ Deploy Preview for set-website ready!

Name	Link
🔨 Latest commit	218f8c1d34dd7ae28e6948422cdf73652aaba5ee
🔍 Latest deploy log	https://app.netlify.com/sites/set-website/deploys/65ba96c05c195000082c3290
😎 Deploy Preview	https://deploy-preview-28--set-website.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions[bot]]

PR Preview Action v1.4.6 :---: :rocket: Deployed preview to https://CU-DBMI.github.io/set-website/preview/pr-28/ on branch gh-pages at 2024-01-31 18:52 UTC

[d33bs]

Background on the nested tables: I tried to find a better way to describe these without tables (using diagramming tools) but found HTML tables to be the plainest / simplest to work with. If there's something else I should use or do for these, please don't hesitate to let me know!

Update: I've moved to images of the rendered tables to work around any potential issues here. The HTML source is preserved within an HTML comment for replicability / modifications.

[vincerubinetti]

Update: I've moved to images of the rendered tables to work around any potential issues here. The HTML source is preserved within an HTML comment for replicability / modifications.

Didn't see this comment until now. Were you seeing any specific issues? If so, it could be a CSS issue with the template. The bucket emojis would look different on different devices but I don't think that's a problem.

[d33bs]

Thank you @vincerubinetti and @falquaddoomi for your reviews and thorough comments! I've made some modifications based on your comments.

[d33bs]

Thank you so much @chrisroederucdenver for your review and further comments to this! I've adjusted the content to be more accurate based on what you mentioned.