I have a couple of inactive Pinax sites at different versions (0.9.x and 0.7.x). These both started with two common features:
While the version of Pinax was the most recent to have a (nonempty)
socialstarter project, they were both relatively old; and:
Installation hinged on procuring some extremely rare and difficult dependencies.
In looking at this, there seems to be a theme of increasing fragility. Dependencies seem to constitute single points of failure, and the trend is to have more and more of them.
Any suggestions about how to cope with this, above creating a virtualenv while you still can? What options should I consider if I want minimize adding (possibly ephemeral) dependencies? Are there ways to estimate how ephemeral a given dependency is?
Possibly with enough duct tape, I might for instance have a gallery of virtualenvs, and ensure that every single version of every single dependency is available in source and installed format.
I'm looking at creating all of a self-contained project with its own "roll your own" apps, not because I think this is desirable or Pythonic in itself, but to quarantine most or all single points of failure to my own code, which ideally should be working and deployable after downloading Python, Django (if needed) and my project alone.