nano

1.1.0 verified Mon Apr 27 auth: no python

Django nano provides loosely coupled mini-apps that do less. Current version 1.1.0, supports Python >=3.9. Newer versions may be available; check PyPI for latest release cadence.

pip install django-nano

Common errors

error ModuleNotFoundError: No module named 'django_nano' ↓

cause Using the deprecated package name 'django_nano' instead of 'nano'.

fix

Run 'pip install django-nano' and import from 'nano' (not 'django_nano').

error django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: nano ↓

cause Multiple apps with label 'nano' in INSTALLED_APPS.

fix

Remove duplicate entries from INSTALLED_APPS; keep only one reference to nano.

error ImportError: cannot import name 'NanoAppConfig' from 'nano' ↓

cause Outdated or broken installation; missing __init__.py or version conflict.

fix

Update django-nano to latest version: 'pip install --upgrade django-nano'.

Warnings

deprecated The old import path 'django_nano' is deprecated in version 1.1.0, use 'nano' instead. ↓

fix Change 'from django_nano import ...' to 'from nano import ...'

gotcha Nano apps require Django's AppConfig to be properly configured; missing app config leads to runtime errors. ↓

fix Ensure 'nano.apps.NanoAppConfig' is in INSTALLED_APPS.

gotcha Nano does not include migrations; you must run makemigrations/manage.py migrate if your nano apps define models. ↓

fix Run 'python manage.py makemigrations' and 'python manage.py migrate' after adding nano apps.

Imports

NanoAppConfig
wrong
```
from django_nano import NanoAppConfig
```
correct
```
from nano import NanoAppConfig
```
Common mistake: using django_nano instead of nano
NanoView
```
from nano.views import NanoView
```
No common wrong import known

Quickstart

Import NanoAppConfig and add it to Django's INSTALLED_APPS.

from nano import NanoAppConfig

# Example: register a nano app in INSTALLED_APPS
# INSTALLED_APPS = ['nano.apps.NanoAppConfig']
print('Nano ready')