<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Through My Eyes (Posts about cpython)</title><link>https://mrinalpurohit.in/</link><description></description><atom:link href="https://mrinalpurohit.in/categories/cpython.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Mon, 18 Aug 2025 20:24:56 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>The Curious Case of Matching Memory Locations in Python</title><link>https://mrinalpurohit.in/blog/the-curious-case-of-matching-memory-locations-in-python/</link><dc:creator>Mrinal Purohit</dc:creator><description>&lt;div&gt;&lt;p&gt;So I attended a Python &lt;a href="https://www.meetup.com/BangPypers/events/238929256/"&gt;meetup&lt;/a&gt;
yesterday which was quite informative and one of the talks which I found
fascinating was about &lt;code&gt;Cleaning the trash in Python&lt;/code&gt; by
Rivas. He starts his talk by explaining what is &lt;code&gt;trash&lt;/code&gt; in
programming sense, and goes on to compare memory allocation for objects
and arrays in C and Python.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://mrinalpurohit.in/blog/the-curious-case-of-matching-memory-locations-in-python/"&gt;Read more…&lt;/a&gt; (3 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>cpython</category><category>memory</category><category>objects</category><category>python</category><category>tips</category><guid>https://mrinalpurohit.in/blog/the-curious-case-of-matching-memory-locations-in-python/</guid><pubDate>Sun, 21 May 2017 11:01:28 GMT</pubDate></item></channel></rss>