fedora-docs-l10n/packaging-guidelines/master/pages/Python — English @ Fedora Weblate: However, this cannot be used for top-level modules (those directly …

Zen

Source string Source string

English

However, this cannot be used for top-level modules (those directly in e.g. `+%{python3_sitelib}+`), because both `+%{python3_sitelib}+` and `+%{python3_sitelib}/__pycache__/+` are owned by Python itself. Here, the `+%pycached+` macro can help. It expands to the given `+*.py+` source file and its corresponding cache file(s). For example:

Needs editing

The string is read only.

Skip

	English	Actions
	The Fedora component (source package) name for a library should be formed by taking the _canonical project name_ and prepending `+python-+` if it does not already start with `+python-+`. This may leads to conflicts (e.g. between https://pypi.org/project/bugzilla/[bugzilla] and https://pypi.org/project/python-bugzilla/[python-bugzilla]). In that case, ensure upstream is aware of the potentially confusing naming and apply best judgment.
	Application naming
	Packages that primarily provide applications, services or any kind of executables SHOULD be named according to the general xref:Naming.adoc[Fedora naming guidelines] (e.g. `+ansible+`).
	Consider adding a virtual provide according to <<Library naming>> above (e.g. `+python3-PROJECTNAME+`), if it would help users find the package.
	Files to include
	Source files and bytecode cache[[_byte_compiling]]
	Packages MUST include the source file (`+.py+`) AND* the bytecode cache (`+.pyc+`) for each pure-Python importable module. The source files MUST* be included in the same package as the bytecode cache.
	Scripts that are not importable (typically ones in `+%{_bindir}+` or `+%{_libexecdir}+`) SHOULD NOT be byte-compiled.
	The cache files are found in a `+__pycache__+` directory and have an interpreter-dependent suffix like `+.cpython-39.pyc+`.
	The cache is not necessary to run the software, but if it is not found, Python will try to create it when a module is imported. If this succeeds, the file is not tracked by RPM and it will linger on the system after uninstallation. If it does not succeed, users can get spurious SELinux AVC denials in the logs.
	Normally, byte compilation (generating the cache files) is done for you by the `+brp-python-bytecompile+` xref:index.adoc#_brp_buildroot_policy_scripts[BRP script], which runs automatically after the `+%install+` section of the spec file has been processed. It byte-compiles any `+.py+` files that it finds in `+%{python3_sitelib}+` or `+%{python3_sitearch}+`.
	You must include these files of your package (i.e. in the `+%files+` section).
	If the code is in a subdirectory (importable package), include the entire directory:
	%files %{python3_sitelib}/foo/
	Adding the trailing slash is best practice for directories.
	However, this cannot be used for top-level modules (those directly in e.g. `+%{python3_sitelib}+`), because both `+%{python3_sitelib}+` and `+%{python3_sitelib}/__pycache__/+` are owned by Python itself. Here, the `+%pycached+` macro can help. It expands to the given `+*.py+` source file and its corresponding cache file(s). For example:
	%files %pycached %{python3_sitelib}/foo.py
	expands roughly to:
	%files %{python3_sitelib}/foo.py %{python3_sitelib}/__pycache__/foo.cpython-3X{,.opt-?}.pyc
	Manual byte compilation[[manual-bytecompilation]]
	If you need to bytecompile stuff outside of `+%{python3_sitelib}+`/`+%{python3_sitearch}+`, use the <<py_byte_compile,`+%py_byte_compile+` macro>>.
	For example, if your software adds `+%{_datadir}/mypackage+` to Python’s import path and imports package `+foo+` from there, you will need to compile `+foo+` with:
	%py_byte_compile %{python3} %{buildroot}%{_datadir}/mypackage/foo/
	Dist-info metadata
	Each Python package MUST include _Package Distribution Metadata_ conforming to https://packaging.python.org/specifications/[PyPA specifications] (specifically, https://packaging.python.org/specifications/recording-installed-packages/[Recording installed projects]).
	The metadata SHOULD be included in the same subpackage as the main importable module, if there is one.
	This applies to libraries (e.g. `+python-requests+`) as well as tools (e.g. `+ansible+`).
	When software is split into several subpackages, it is OK to only ship metadata in one built RPM. In this case, consider working with upstream to also split the upstream project.
	The metadata takes the form of a `+.dist-info+` directory installed in `+%{python3_sitelib}+` or `+%{python3_sitearch}+`, and contains information that tools like https://docs.python.org/3/library/importlib.metadata.html[`+importlib.metadata+`] use to introspect installed libraries.
	For example, a project named `+MyLib+` with importable package `+mylib+` could be packaged with:
	%files -p python3-mylib %{python3_sitelib}/mylib/ %{python3_sitelib}/MyLib-%{version}.dist-info/ %doc README.md %license LICENSE.txt

Loading…

No matching activity found.

Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English	English
No related strings found in the glossary.

8316482 String information

Source string description

type: Plain text

Flags

placeholders:r"`pass:\[.\]`":r"\`\+[\w\d/\*-_%\.{}\(\) \']*\+\`":r"`[\w-]*`":r"xref\:[\w\d_-]*(\.adoc)?(#[\w\d_-]*)?":r"\[\[[\w_-]*\]\]", read-only

Source string location

./pages/Python.adoc:383

String age

3 years ago

Last updated

3 months ago

Source string age

3 years ago

Translation file

pot/master/pages/Python.pot, string 76

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.