<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Python on rkempe’s blog</title>
    <link>https://blog.rkempe.ca/tags/python/</link>
    <description>Recent content in Python on rkempe’s blog</description>
    <generator>Hugo</generator>
    <language>en-ca</language>
    <copyright>&amp;copy; Copyright 2026 Rebecca Kempe</copyright>
    <lastBuildDate>Sun, 24 Nov 2024 00:28:41 -0500</lastBuildDate>
    <atom:link href="https://blog.rkempe.ca/tags/python/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding the Python Memory Model</title>
      <link>https://blog.rkempe.ca/posts/2024/11/understanding-the-python-memory-model/</link>
      <pubDate>Sun, 24 Nov 2024 00:28:41 -0500</pubDate>
      <guid>https://blog.rkempe.ca/posts/2024/11/understanding-the-python-memory-model/</guid>
      <description>One of my quests during the research project I did last summer was to find a way to simulate pointers in Python, or at the very least, get some sort of named reference-like behaviour from the language. Unfortunately, I quickly learned that this is quasi-impossible, because Python is a language that aims to abstract as many implementation details away from the user as possible, and gives programmers very limited ways in which to interact with the language.</description>
    </item>
  </channel>
</rss>
