<?xml version="1.0" encoding="utf-8"?>



<feed xmlns="http://www.w3.org/2005/Atom"
    xmlns:fh="http://purl.org/syndication/history/1.0"
    xmlns:at="http://purl.org/atompub/tombstones/1.0">

    <title>Publ: Development Blog</title>
    <subtitle>A personal publishing system for the modern web</subtitle>
    <link href="http://publ.beesbuzz.biz/blog/feed?tag=post-mortem" rel="self" />
    <link href="http://publ.beesbuzz.biz/blog/feed" rel="current" />
    <link href="https://busybee.superfeedr.com" rel="hub" />
    
    
    <link href="http://publ.beesbuzz.biz/blog/" />
    <fh:archive />
    <id>tag:publ.beesbuzz.biz,2020-01-07:blog</id>
    <updated>2018-05-02T22:56:59-07:00</updated>

    
    <entry>
        <title>Well, that was embarrassing...</title>
        <link href="http://publ.beesbuzz.biz/blog/216-Well-that-was-embarrassing" rel="alternate" type="text/html" />
        <published>2018-05-02T22:56:59-07:00</published>
        <updated>2018-05-02T22:56:59-07:00</updated>
        <id>urn:uuid:55415435-a738-488b-b407-d140bb040c2c</id>
        <author><name>fluffy</name></author>
        <content type="html">
<![CDATA[
<p>So, note to self: library version pinning is a good idea. I should also learn how to properly manage my library version dependencies.</p><p>Thanks to <a href="https://twitter.com/therealtakeshi">@therealtakeshi</a> for <a href="https://twitter.com/therealtakeshi/status/991908218686377984">bringing this to my attention</a>!</p>

<p>The short version of what brought this site down was that, as far as I can tell, Flask-Cache pushed out an
update that finally removed a deprecated namespace. Unfortunately, that namespace was still in use by Flask-Cache itself.
So, presumably this means that any Flask app that&rsquo;s using an unpinned version of Flask-Cache is going to break as
soon as they update their dependencies. Oops.</p><p>Word on the street is that Flask-Cache is basically abandoned anyway so for now I&rsquo;ve switched to flask_caching.</p><p>Oh and investigating this I realized the caching config <a href="https://github.com/fluffy-critter/Publ/issues/61">wasn&rsquo;t actually being applied anyway</a>,
so caching was disabled. Whoops. Anyway I&rsquo;ve fixed that (which will be part of the next version, likely 0.1.8).</p>

]]>
        </content>
    </entry>
    

    
</feed>