Message 50491 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	lars.gustaebel
Recipients
Date	2006-12-30.12:11:44
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
In order to determine the current umask we have no other choice AFAIK than to set it with a bogus value, save the return value and restore it right away - as you proposed in your patch. The problem is that there is a small window of time between these two calls where the umask is invalid. This is especially bad in multi-threaded environments. Any ideas?

In order to determine the current umask we have no other choice AFAIK than to set it with a bogus value, save the return value and restore it right away - as you proposed in your patch. The problem is that there is a small window of time between these two calls where the umask is invalid. This is especially bad in multi-threaded environments.

Any ideas?

History
Date	User	Action	Args
2007-08-23 15:52:52	admin	link	issue1507247 messages
2007-08-23 15:52:52	admin	create