#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
---------------------------------+------------------------------------
Comment (by Carlton Gibson):
Hi Leon.
[https://github.com/GrahamDumpleton/mod_wsgi/issues/675#issuecomment-840181867
Graham replied on `mod_wsgi`]:
> For now try setting:
> WSGIRestrictedStdout Off
He also points out there where `colorama` can catch the OSError
([https://github.com/tartley/colorama/issues/304 Matching colorama issue])
Can you give the PR on https://github.com/django/django/pull/14386 a go.
That should at least enable you to get past this with
`WSGIRestrictedStdout` still on.
We're looking into whether we can move the `colorama.init()` off the
import-time path. (It's meant to be a no-op on other platforms, but is
hitting this OSError issue from mod_wsgi...)
--
Ticket URL: <https://code.djangoproject.com/ticket/32740#comment:6>
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.c3b810357da89fec919aea406f0f3f44%40djangoproject.com.
