Bug #17106
closedSUSE builds do not create __pycache__ files
0%
Description
Credits to Tim Serong for finding this bug.
https://github.com/ceph/ceph/commit/73042684 added packages for Python 3 bindings, including packaging some files in __pycache__ directories. This is in accordance with Fedora packaging guidelines [1].
I assume these __pycache__ directories and the files they contain are created only when the build machine is connected to the network. (That's the most obvious explanation for why they are not created in OBS builds.)
Since these directories/files will be created automatically if they are missing, they can be safely omitted in SUSE builds - at least for now.
[1]
https://fedoraproject.org/wiki/Packaging:Python
"When packaging python modules, several types of files are included:
*.pyc and *.pyo byte compiled files (and, if present, the enclosing __pycache__ directory in most cases)."
Updated by Nathan Cutler over 7 years ago
- Source changed from other to Community (dev)
Updated by Tim Serong over 7 years ago
Ah, that means https://github.com/ceph/ceph/pull/10805 will probably need an "%if ! 0%{?suse_version}" guard...
Updated by Nathan Cutler over 7 years ago
- Status changed from New to In Progress
https://github.com/ceph/ceph/pull/10805 was merged, but in the meantime dimstar77 suggested a way to force creation of the __pycache__ in the spec file.
Updated by Nathan Cutler over 7 years ago
- Status changed from In Progress to 7
master PR: https://github.com/ceph/ceph/pull/10894