<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Python on WT8P&#39;s Notes to Self</title>
    <link>https://wt8p.com/tags/python/</link>
    <description>Recent content in Python on WT8P&#39;s Notes to Self</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Dec 2019 18:57:00 +0000</lastBuildDate>
    <atom:link href="https://wt8p.com/tags/python/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Determining the exact file python is using</title>
      <link>https://wt8p.com/determining-the-exact-file-python-is-using/</link>
      <pubDate>Wed, 04 Dec 2019 18:57:00 +0000</pubDate>
      <guid>https://wt8p.com/determining-the-exact-file-python-is-using/</guid>
      <description>&lt;p&gt;Python searches a variety of directories for its libraries, something I had largely lived in peace with until I had to modify some legacy code to address a suspected timing bug.&lt;/p&gt;
&lt;p&gt;The overall task is to produce a set of charts for a customer. Python loads an Excel workbook, a time-series data set is updated from a third-party source, and a Visual Basic Excel macro iterates through the workbook’s numerous tabs, adjusts to fiscal quarters, and emits several dozen charts. It’s clunky, but what I was given to work with. Until recently, was functioning well-enough.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
