On Mon, Jul 15, 2013 at 3:02 PM, Juan Luis Boya wrote:
> I've posted a patch for runfcgi here:
>
> https://code.djangoproject.com/ticket/20751
>
> It includes documentation update and unit tests, for anyone interested, if
> any.
Juan Luis,
This is all great work. Thank you
I've posted a patch for runfcgi here:
https://code.djangoproject.com/ticket/20751
It includes documentation update and unit tests, for anyone interested, if
any.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this
Hi Juan,
Thanks for your detailed examination and report. The best way to proceed is
definitely to create a ticket in trac:
https://code.djangoproject.com/newticket .
Then, if you are willing and like to become a contributor, you can either
add a patch or create a pull request on github.
yes. i agree. my tests in hostgator.com shared host show this. tests
in my ubuntu 12.04 amd64 shows same problem. using django 1.5 and
1.6a, 16b.
2013/6/30 Juan Luis Boya :
> They talk about there was a os.umask(0) and they created that option in
> order to change it.
>
> But I
They talk about there was a os.umask(0) and they created that option in
order to change it.
But I would like to know then, why was that `os.umask(0)` there in the
first place? What was it purpose?
On the other hand there is the confusion this option brings. Many people
think the option is
git blame on the line that sets the umask shows it was as a result of
ticket #6994:
https://code.djangoproject.com/ticket/6994
Discussion in that ticket is probably the best information you are going to
get on rationale.
Karen
--
You received this message because you are subscribed to the