#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 Leon Matthews):
Replying to [comment:6 Carlton Gibson]:
> 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.
Thank you Carlton, I'm back at work now, so I'll check that out and get
back to you soon.
> We're looking into whether we can move the `colorama.init()` off the
import-time path.
I agree that that would be cleanest approach. It would be entirely
reasonable to hit this error if my production configuration used the
feature (as my development configuration does).
--
Ticket URL: <https://code.djangoproject.com/ticket/32740#comment:7>
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.727c3998eae4d8d2985fa19445f71c44%40djangoproject.com.
