[JoeAltmaier]

Any older product will fall into disrepair, simply due to the decreased attention old features get. Plus the years of accumulated of references to any particular feature, that would take years to track and put right whenever it changes.

Not sure there's any cure.

I hit this (OP) issue myself. Solved it somehow, don't remember, just another glitch in the neverending series of glitches that are open-source lack-of-support and obsolete documentation.

Just today, noticed Steam tutorial videos generally use some obsolete version of their website tools. Have to fish around, find where the menus etc are, they sure aren't where the video says they are.

Business as usual.

[dekhn]

The cure is to put a test on it (beyonce rule), and make the test passing required for release. And do rapid rollbacks (within 1 day) if bad releases are made.

[JoeAltmaier]

If you own all the code, sure.

But big things (OS, framework etc) have code squirreled away all over the world.

[paulddraper]

Flask puts a test on someone else's unmaintained pacakge?

[dekhn]

In this case, I would expect that the author of this post (who, IIUC is also the creator of flask), should have a test case that trips/fails within a day of the tutorial becoming invalid. At least then he knows the tutorial is going to fail for users.

I was burned by flask/werkzeug enough times to completely avoid flask unless absolutely neccessary.