extract heights.json and fix manage.py to use uv

manage.py

@@ -1,4 +1,15 @@
 #!/usr/bin/env python
+# /// script
+# requires-python = ">=3.13"
+# dependencies = [
+#     "bs4",
+#     "cryptography",
+#     "django",
+#     "piexif",
+#     "pillow",
+#     "unidecode",
+# ]
+# ///
 import os
 import sys
 

pre-run.sh

@@ -1,7 +1,7 @@
 #! /bin/bash
 # Do these before final testing, *not* just before pushing:
-# Need to be in an ALREADY activated venv
+# Changed to use uv not pip, requires manage.py to have uv structured uv comment in it.
-PYTHON="python"
+PYTHON="uv run"
 
 echo "** Run inspectdb:"
 $PYTHON manage.py inspectdb > troggle-inspectdb.py
@@ -30,7 +30,7 @@ echo "** Now running test suite"
 # $PYTHON manage.py test -v 1
 
 echo ""
-echo `tail -1 lines-of-python.txt`   non-comment lines of python. But core/utils.py has 28,000 lines of numbers.
+echo `tail -1 lines-of-python.txt`   non-comment lines of python. 
 echo `tail -1 lines-of-templates.txt`   non-comment lines of HTML templates.
 
-echo '** If you have an error running manage.py, maybe you are not in an activated venv ?'
+echo '** If you have an error running manage.py, maybe you are not in an activated venv ? or your manage.py is not managed by uv properly ?'

security-warnings.txt

@@ -1,10 +1,10 @@
+Reading inline script metadata from `manage.py`
 System check identified some issues:
 
 WARNINGS:
 ?: (security.W001) You do not have 'django.middleware.security.SecurityMiddleware' in your MIDDLEWARE so the SECURE_HSTS_SECONDS, SECURE_CONTENT_TYPE_NOSNIFF, SECURE_REFERRER_POLICY, SECURE_CROSS_ORIGIN_OPENER_POLICY, and SECURE_SSL_REDIRECT settings will have no effect.
-?: (security.W009) Your SECRET_KEY has less than 50 characters, less than 5 unique characters, or it's prefixed with 'django-insecure-' indicating that it was generated automatically by Django. Please generate a long and random value, otherwise many of Django's security-critical features will be vulnerable to attack.
 ?: (security.W012) SESSION_COOKIE_SECURE is not set to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.
 ?: (security.W016) You have 'django.middleware.csrf.CsrfViewMiddleware' in your MIDDLEWARE, but you have not set CSRF_COOKIE_SECURE to True. Using a secure-only CSRF cookie makes it more difficult for network traffic sniffers to steal the CSRF token.
 ?: (security.W018) You should not have DEBUG set to True in deployment.
 
-System check identified 5 issues (0 silenced).
+System check identified 4 issues (0 silenced).