Use a custom umask when running buildout.
This extension allows better control over the initial permissions of files created by buildout by allowing the umask used by the buildout script to be specified in the configuration file.
Because of bug 180705 of zc.buildout, this doesn’t work for scripts installed by buildout.
This doesn’t affect the umask of other scripts in the buildout, unless they set their own the umask of the user running them will be used, e.g.: ZEO/Zope might still make var/filestore/Datafile.fs world readable if your umask is 022.
[buildout] extensions = buildout.umask umask = 027
The umask parameter can be specified using any of Python conventions for numeric literals of binary, octal, decimal or hexadecimal radix. If any of them is used and a 0 is the first digit, octal is assumed as well.
The code is quite simple, take a glimpse.
- Documentation fixes.
- Fix packaging by using setuptools_bzr.
- First public release
- Initial version.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size buildout.umask-0.5.2.tar.gz (2.7 kB)||File type Source||Python version None||Upload date||Hashes View|