On Sep 22, 7:12 pm, Anthon <anthon.van.der.n...@googlemail.com> wrote:
> Is anyone using the versioning feature?
> It seems currently broken out of the box on my mod_wsgi/apache system.
> The main problem exists because mercurial writes to sys.stdout if some
> warning/error occurs.
> On my fresh system I get those writes because of two issues:
> - non existence of a username in ~/.hgrc for the user running apache
> - readding already added files
>
> The one thing you can do is to capture sys.stdout in mercurial.py:
> commit,
> but that hides all messages/error writing from mercurial.
> The two issues can be resolved differently:
> - by checking for the .hgrc and setting HGUSER if it is not available
> - by using a .hgignore file and not adding an explicit list in
> mercurial.py but using hg addremove option (that is also much nicer
> when doing mercurial commands in the application directory from the
> commandline as it hides all the non-tracked data)
>
> I can provide a patch if there is interest in this way of solving this
> issue
Read the documentation:
http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Writing_To_Standard_Output
and my blog posts about it:
http://blog.dscpl.com.au/2009/04/wsgi-and-printing-to-standard-output.html
Make sure you also aren't using an old mod_wsgi version.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
