#23879: We should use test-skipping, not conditional discovery in runtests.py
--------------------------------------+------------------------------------
Reporter: carljm | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Testing framework | Version: master
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
--------------------------------------+------------------------------------
Comment (by carljm):
I agree. I think there are probably some aspects that require further
thought (like what happens if a later migration is "appropriate for this
connection" but has a dependency on one that is not?), but I think the
general idea is sound.
I wonder if perhaps it would work better if it were operations rather than
entire migrations that were marked as for-certain-db-vendor-only? I could
imagine some API like a mark-for-vender wrapper to surround a list of
operations in a migration file.
--
Ticket URL: <https://code.djangoproject.com/ticket/23879#comment:8>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.ea1d9c2f08a90cb4bb0a40e21fa0a155%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
