ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #django
Goal I want a reliable way to run Django integration tests that exercise code paths normally talking to external services (email, cache, payment or storage APIs) without ever loading production credentials. The project currently relies on environment variables for secrets, and the test suite uses override_settings in places, but there is no enforced project-
On supported Django versions, restoring a project can follow two distinct paths: ORM-level fixture serialization via dumpdata and loaddata , or database-native backup and restore tooling. The interoperability question is how to verify recovered data across the boundary between these two sources, since they capture different state. loaddata merges rather than
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested docker: Error response from daemon: could not select device driver "" with capabilities: [[gpu]]. I am facing this error on mac while trying to run this command docker run --rm --gpus all -v static_volume:/ho
In Django, the development server automatically serves static files when DEBUG is set to True. However, when transitioning to a production environment, the framework relies on the collectstatic command to aggregate assets into a physical directory defined by STATIC_ROOT . A common discrepancy arises when STATIC_ROOT is correctly configured in settings but th
I'm developing a Django (2.2.3) application with Django Microsoft Auth installed to handle SSO with Azure AD. I've been able to follow the quickstart documentation to allow me to log into the Django Admin panel by either using my Microsoft identity, or a standard username and password I've added to the Django user table. This all works out of the box and is
Django's timezone framework converts naive datetimes to UTC for storage when USE_TZ=True , assuming they belong to TIME_ZONE . During daylight-saving fall-back transitions, a local time such as 01:30 can occur twice, creating an ambiguous instant. The documentation acknowledges this overlap but does not define a deterministic resolution rule for django.utils
I am running a linux red hat environment from AWS. I have followed every instruction for upgrading sqlite3 to the "latest" version. I am running python 3.9.2 (and have recompiled it with LD_RUN_PATH=/usr/local/lib ./configure ) and django version 4. I have set up a virtual environment to install and run django. I have changed the activate script to include e
I am designing an async view running under ASGI (Django 4.2+ assumed) that performs several awaits plus one expensive synchronous computation. My understanding is that when the client disconnects, the ASGI server cancels the request task and asyncio.CancelledError propagates — but only at the next await point. Blocking sync work inside the coroutine would de
Django's ASGI handler cancels an async view's coroutine when the client disconnects, raising asyncio.CancelledError at the next await point. Cleanup in async views is therefore expected to happen in try/finally blocks that also account for CancelledError inheriting from BaseException since Python 3.8. The unresolved behavior involves the ORM. Database calls
docker
nginx
azure