#24648: Model fields that reference settings that differ between dev and prod
trigger the autodetector
--------------------------------------+------------------------------------
Reporter: Xof | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):
* cc: andrewgodwin (added)
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
One idea (not sure if it would cause problems) is to modify the migration
file to replace the literal value `'/content/'` with a reference to the
setting, `settings.UPLOAD_URL`. If so, we could document this.
--
Ticket URL: <https://code.djangoproject.com/ticket/24648#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.92a3aabf5d9c1edc0ae2f7919ac52295%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
