Opened 18 years ago
Closed 18 years ago
#3892 closed (wontfix)
Django should implement PEP-87082 and become self-aware.
Reported by: | Avril F. | Owned by: | Jacob |
---|---|---|---|
Component: | Core (Cache system) | Version: | dev |
Severity: | Keywords: | django, pep, | |
Cc: | Triage Stage: | Design decision needed | |
Has patch: | no | Needs documentation: | yes |
Needs tests: | yes | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
PEP-87082 discusses the planned roadmap for beyond Python 5000b. As the premiere python web framework, Django needs to be compliant to the BDFL's plans for the future.
Step 1: the cache framework should be expanded to handle scientific notation.
To survive into the year 5 billion, Django will need a long-term caching system for both data and hardware. Unfortunately, the current caching framework, whilst excellent, is not designed for caching on the billions-of-years timescale, since this will require the cache length parameter to be specified in scientific notation (1.5778463 × 1017 to be precise.)
I recommend we enhance the current functionality with exponential notation:
CACHE_BACKEND = "memcached://127.0.0.1:11211/?timeout=1.5778463x10^17&max_entries=10000000"
Step 2: Provide some pickle mechanism for the server.
To survive the forthcoming apocalypse, the servers running Django instances will need to be "stored" somehow. Past experience shows that a stone/rock-based encoding system has a proven track record of long-term fidelity. I propose
we implement a create_stonehenge()
method for storing the server information in a non-digital framework. We can look to the Cobol community for experience with this sort of stuff.
Step 3: Facilitate self-awareness in Django.
Once the two caching issues above are solved, we need to dedicate our time to ensuring that there is some recovery mechanism for un-stonehenging the server and retrieving the cache. Previous research has shown that the best solution for surviving nuclear holocausts and other apocalyptic events is to become self-aware
. We should implement a neural-network based solution, and allow this to slowly trained, with the aim of it becoming self-maintaining by at least 2075.
If these steps are taken, I am confident that Django will become the world's premiere (and only) web development framework for perfectionists, of whatever type evolves once humanity has been wiped out.
Change History (2)
comment:1 by , 18 years ago
Needs documentation: | set |
---|---|
Needs tests: | set |
Patch needs improvement: | set |
Triage Stage: | Unreviewed → Design decision needed |
comment:2 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Ok, the fun is over for another year. :-)