Version 2.77 package for OS X contains non-modifiable __pycache__ directories #47875

New Issue

Hannes Juutilainen · 2016-03-21T08:59:20+01:00

2016-03-21 08:59:20 +01:00

System Information
OS X 10.11

Blender Version
Broken: 2.77
Worked: 2.76

Short description of error
The latest version 2.77 seems to include pycache directories for all Python libraries and all of them have dr-xr-xr-x permissions (the owner can not write). Is this intentional? As a result the blender.app or blenderPlayer.app can not be removed unless the permissions are changed (by running chmod -R u+w). Please note that moving the files to trash by using Finder and the emptying the trash seems to work.

Exact steps for others to reproduce the error
Download the OS X version from the main download site. Unarchive it and try to remove the Blender directory from command line by running rm -rf <path_to_blender>.

**System Information** OS X 10.11 **Blender Version** Broken: 2.77 Worked: 2.76 **Short description of error** The latest version 2.77 seems to include __pycache__ directories for all Python libraries and all of them have dr-xr-xr-x permissions (the owner can not write). Is this intentional? As a result the blender.app or blenderPlayer.app can not be removed unless the permissions are changed (by running `chmod -R u+w`). Please note that moving the files to trash by using Finder and the emptying the trash seems to work. **Exact steps for others to reproduce the error** Download the OS X version from the main download site. Unarchive it and try to remove the Blender directory from command line by running `rm -rf <path_to_blender>`.

Hannes Juutilainen commented

2016-03-21 08:59:20 +01:00

Changed status to: 'Open'

Hannes Juutilainen commented

2016-03-21 08:59:20 +01:00

Added subscriber: @hjuutilainen

Martijn Berger commented

2016-03-21 11:51:08 +01:00

Added subscriber: @MartijnBerger

Martijn Berger commented

2016-03-21 11:51:08 +01:00

If the files in those directories change the application signature will not be valid.
We need to fix this for next release by moving the python files and caches to a more appropriate path.

If the files in those directories change the application signature will not be valid. We need to fix this for next release by moving the python files and caches to a more appropriate path.

Campbell Barton commented

2016-03-21 13:37:35 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2016-03-21 13:37:35 +01:00

Wasn't pre-compiling __pycache__ intentional?, AFAIK these shouldn't have to be re-generated.

Wasn't pre-compiling `__pycache__` intentional?, AFAIK these shouldn't have to be re-generated.

Martijn Berger commented

2016-03-21 15:50:24 +01:00

They are not regenerated and we generated them intentional.
The permissions on the folders they are in are non writable so they should not be regenerated ever as blender would not be able to write to them anyway.

We should ship the python stuff and extract that to ~/Library/application support on first run and that way keep it out of blender.app's bundle to work around these signing rules better.

They are not regenerated and we generated them intentional. The permissions on the folders they are in are non writable so they should not be regenerated ever as blender would not be able to write to them anyway. We should ship the python stuff and extract that to ~/Library/application support on first run and that way keep it out of blender.app's bundle to work around these signing rules better.

Hannes Juutilainen commented

2016-03-21 16:46:13 +01:00

Thank you for explaining this. When we deploy Blender to lab machines (or any other OS X machine) the files get copied to /Applications directory and the owner is set to root:wheel recursively. So in mass deployment situations Blender has never had a chance to write inside its own application bundle.

Would these cache files be recreated in some user space temp location if they were missing from the app bundle and user did not have write access to the folder?

Thank you for explaining this. When we deploy Blender to lab machines (or any other OS X machine) the files get copied to /Applications directory and the owner is set to root:wheel recursively. So in mass deployment situations Blender has never had a chance to write inside its own application bundle. Would these cache files be recreated in some user space temp location if they were missing from the app bundle and user did not have write access to the folder?

Campbell Barton commented

2016-03-21 17:34:53 +01:00

Would these cache files be recreated in some user space temp location if they were missing from the app bundle and user did not have write access to the folder?

No, they just won't get created in that case - It will still work, just a little slower startup since Python modules won't be cached.

> Would these cache files be recreated in some user space temp location if they were missing from the app bundle and user did not have write access to the folder? No, they just won't get created in that case - It will still work, just a little slower startup since Python modules won't be cached.

Sergey Sharybin commented

2016-03-22 13:02:43 +01:00

Added subscriber: @Sergey

Martijn Berger was assigned by Sergey Sharybin

2016-03-22 13:02:43 +01:00

Sergey Sharybin commented

2016-03-22 13:02:43 +01:00

So it is a real issue to be addressed or more like a TODO?

Martijn Berger was unassigned by Dalai Felinto

2019-12-23 16:37:11 +01:00

Sybren A. Stüvel commented

2020-02-04 11:07:44 +01:00