#25011: Running unit tests on Mac takes me down a GDAL installation rabbit hole
-------------------------------------+-------------------------------------
Reporter: nedbat | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Testing framework | Version: master
Severity: Normal | Resolution: duplicate
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):
It's not a big deal, and I'm sure it's true that the PR won't get lost,
but I think Ned is right, and there wasn't a good reason to close this
ticket as a duplicate (especially as a duplicate of a ticket it clearly
isn't a duplicate of - "problem caused by fix for some other ticket" is
not the same thing as "duplicate").
If there's a known problem in master (which there is right now), a ticket
with a clear description of that problem (which this is) should be left
open until a fix for the problem is merged to master. And that fix should
reference the ticket which is a clear description of the problem it's
fixing (and perhaps also the original ticket whose fix caused the problem
in the first place.)
--
Ticket URL: <https://code.djangoproject.com/ticket/25011#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 [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/064.60de3f86771fab4cb1948fd69adc2c82%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
