dj-inmemorystorage
A non-persistent in-memory data storage backend for Django.
Decision gist · record as of 2026-08-14
Yes, if your Django and Python versions fall within the supported range (Django 1.11–3.0, Python 2.7 or 3.5–3.8) and you need a lightweight in-memory storage backend for testing. The permissive BSD license and zero known vulnerabilities are favorable. However, the package is abandoned and will not receive updates for modern Django or Python versions, so it is not suitable for new projects targeting current releases.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Django and six as runtime dependencies; version support is limited to Python 2.7 with Django 1.11, or Python 3.5–3.8 with Django 1.11–3.0.
- Low install friction with a pure-Python wheel.
- However, the package is abandoned—last release was 2020-03-30, over six years ago.
License · maintenance · safety
BSD (permissive) — BSD license (permissive) places no restrictions on use, modification, or distribution in your own projects.
last release 2020-03-30 (2328 days) · last repo commit 2023-06-15 · 52 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 227,403 downloads/mo, #9,179 on PyPI
Alternatives
Verify before relying
# In Django test settings:
DEFAULT_FILE_STORAGE = 'inmemorystorage.InMemoryStorage'
# Optional: enable persistence across storage instances
INMEMORYSTORAGE_PERSIST = True- Whether the package works with Django versions released after 3.0 or Python versions after 3.8.
- Whether the non-persistent default behavior (data not shared across storage instances) meets your test isolation needs.
- Whether the package's archived repository status means it will accept pull requests or security patches.
What it is and what it does
dj-inmemorystorage provides a Django storage backend that keeps file data in memory rather than writing to disk. It implements Django's standard storage API, making it a drop-in replacement for testing scenarios where you want to avoid filesystem I/O. By default, each storage instance maintains its own isolated in-memory state; writes from one part of your code are not visible to another unless they share the same backend instance. You can enable persistence across instances by setting INMEMORYSTORAGE_PERSIST = True in your Django settings.
The package depends on Django and six, and is distributed as a pure-Python wheel with low install friction. However, it has been abandoned since 2020 and receives no maintenance. It was last tested against Django up to version 3.0 and Python up to 3.8, so compatibility with modern versions is unknown.
Use it for
- Unit testing Django applications without writing temporary files to disk during test runs.
- Mocking file uploads in integration tests while keeping test data isolated between test cases.
- Developing and testing Django apps in environments where filesystem access is restricted or slow.
- Rapid prototyping of Django file-handling logic without managing temporary file cleanup.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if your Django and Python versions fall within the supported range (Django 1.11–3.0, Python 2.7 or 3.5–3.8) and you need a lightweight in-memory storage backend for testing.
The permissive BSD license and zero known vulnerabilities are favorable. However, the package is abandoned and will not receive updates for modern Django or Python versions, so it is not suitable for new projects targeting current releases.
Install
dj-inmemorystorage on PyPI
Before you install
Low install friction with a pure-Python wheel. However, the package is abandoned—last release was 2020-03-30, over six years ago. It remains marked Production/Stable and has no known vulnerabilities, but receives no maintenance updates.
Requires Django and six as runtime dependencies; version support is limited to Python 2.7 with Django 1.11, or Python 3.5–3.8 with Django 1.11–3.0.
License in practice
BSD license (permissive) places no restrictions on use, modification, or distribution in your own projects.
Quickstart
# In Django test settings:
DEFAULT_FILE_STORAGE = 'inmemorystorage.InMemoryStorage'
# Optional: enable persistence across storage instances
INMEMORYSTORAGE_PERSIST = TrueVerify before relying
- Whether the package works with Django versions released after 3.0 or Python versions after 3.8.
- Whether the non-persistent default behavior (data not shared across storage instances) meets your test isolation needs.
- Whether the package's archived repository status means it will accept pull requests or security patches.
Package facts
| License | BSD permissive |
| Python support | Not specified |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 2 packagesDjangosix |
| Maintenance | Abandoned 2,328 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 227,403 / month, #9,179 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Development Status :: 5 - Production/StableFramework :: DjangoFramework :: Django :: 1.11Framework :: Django :: 2.0Framework :: Django :: 2.1Framework :: Django :: 2.2Framework :: Django :: 3.0Intended Audience :: DevelopersLicense :: OSI Approved :: BSD LicenseOperating System :: OS IndependentProgramming Language :: PythonProgramming Language :: Python :: 2Programming Language :: Python :: 2.7Programming Language :: Python :: 3Programming Language :: Python :: 3.5Programming Language :: Python :: 3.6Programming Language :: Python :: 3.7Programming Language :: Python :: 3.8Topic :: Internet :: WWW/HTTP |
Evidence: dj_inmemorystorage-2.1.0-py2.py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “django in-memory storage”
- dj-inmemorystorageAn in-memory storage backend for Django that implements Django's…
- django-redisProvides a Redis cache and session backend for Django, supporting…
- django-valkeyProvides a Valkey cache and session backend for Django, allowing you…
Give your agent the search over MCP, or paste the wish link into any chat.
More WWW/HTTP packages
urllib3 is an HTTP client library that provides thread-safe connection pooling, SSL/TLS verification, multipart file uploads, request retries, compression support, and proxy handling for Python applications.
Requests is a Python HTTP library that simplifies sending HTTP/1.1 requests with automatic handling of headers, authentication, cookies, and response parsing.
h11 is a pure-Python HTTP/1.1 protocol implementation that handles parsing and serializing HTTP messages without any built-in I/O, letting you integrate it with any network layer you choose.
HTTPX is a fully featured HTTP client library for Python that provides both sync and async APIs, with support for HTTP/1.1 and HTTP/2, plus an integrated command-line client.
Install it if you are building new projects or modernizing existing ones that rely on HTTP.
A minimal low-level HTTP client library that sends HTTP requests with thread-safe and task-safe connection pooling, supporting HTTP/1.1, HTTP/2, proxies, and both sync and async interfaces.
aiohttp is an async HTTP client and server framework built on asyncio, supporting both WebSockets and middleware-based routing for building concurrent web applications.
Install it if you need async HTTP client or server capabilities in asyncio-based applications.
See also django-crum · django-memoize · django-cache-memoize · django-sortedm2m · dj-static · django-multiselectfield · djangorestframework-gis · django-impersonate · django-safedelete · django-netfields