Printing to stdout breaks webapp when running behind modwsgi

Anonymous avatarAnonymous created an issue


We're running a web service using modwsgi, and this service used django-piston to provide its REST APIs.

Some of our resources are protected using OAuthAuthentication, and the current source code has a print statement inside the is_authenticated method:

When the services is run and tests locally, everything works fine. When run in the production environment, which uses modwsgi, we get 500 when accesing the API since modwsgi fails due to the attempt to write to sys.stdout.

Is there any chance to make this piston code not to write to stdout? Ideally a logging setup should be used instead, specially if this is for debugging purpouses.


Comments (0)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.