#32740: Running colorama.init() at import time causes deployment error
---------------------------------+------------------------------------
Reporter: Leon Matthews | Owner: nobody
Type: Bug | Status: new
Component: Core (Other) | Version: 3.2
Severity: Release blocker | Resolution:
Keywords: apache mod_wsgi | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by Carlton Gibson):
* severity: Normal => Release blocker
Comment:
[https://github.com/django/django/pull/14386 PR with the try-catch
thought...] — Not at all sure how best to test that. Any thoughts welcome.
> What about avoiding calling colorama.init() on non-Windows platforms?
Yes... maybe… not sure.
There's no reason to have colorama installed at all if you're not on
Windows. So I'd prefer to push back a bit before we do too much: why is it
getting installed at all?; why is mod_wsgi raising for just the `closed`
check?; what do colorama say on this, since presumably they'd like to be
safe on other platforms? 🤔
We can work around this, but I'm not sure it's our issue. It probably
counts as a Release Blocker if we're going to address it though.
--
Ticket URL: <https://code.djangoproject.com/ticket/32740#comment:5>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.aff1ca528a2eb0f46c73c07e50635475%40djangoproject.com.
