fedora-docs-l10n/packaging-guidelines/master/pages/Python

Zen

Translation

English type: Title ==

Finnish

Needs editing

Skip

	English	Finnish	Actions
	`+%{python3}+` (`+/usr/bin/python3+`): The Python interpreter. For example, this macro should be used for invoking Python from a `+spec+` file script, passed to `+configure+` scripts to select a Python executable, or used as `+%{python3} -m pip+` to run a Python-based tool.
	If the packaged software invokes Python at _run time_ (as opposed to running Python to build/test it), it might be necessary to pass flags to `+%{python3}+` to isolate it from user-installed packages. See <<Shebangs>> for details.
	`+%{python3_version}+` (e.g. `+3.9+`, `+3.10+`): Version of the Python interpreter.
	`+%{python3_version_nodots}+` (e.g. `+39+`, `+310+`): Version of the Python interpreter without the dot.
	`+%{python3_sitelib}+` (e.g. `+/usr/lib/python3.9/site-packages+`): Where pure-Python modules are installed.
	`+%{python3_sitearch}+` (e.g. `+/usr/lib64/python3.9/site-packages+`): Where Python extension modules (native code, e.g. compiled from C) are installed.
	The rest of this document uses these macros, along with `+%{_bindir}+` (`+/usr/bin/+`), instead of the raw path names.
	Python implementation support[[_multiple_python_runtimes]]
	Fedora primarily targets _CPython_, the reference implementation of the Python language. We generally use “Python” to mean CPython.
	Alternate implementations like `+pypy+` are available, but currently lack comprehensive tooling and guidelines for packaging. When targetting these, there are no hard rules (except the general Fedora packaging guidelines). But please try to abide by the _spirit_ of these guidelines. When in doubt, consider consulting the Python SIG.
	Python version support
	Fedora packages MUST NOT depend on other versions of the CPython interpreter than the current `+python3+`.
	In Fedora, Python libraries are packaged for a single version of Python, called `+python3+`. For example, in Fedora 32, `+python3+` is Python 3.8.
	In the past, there were multiple Python stacks, e.g. `+python3.7+` and `+python2.7+`, installable together on the same machine. That is also the case in some projects that build _on top_ of Fedora, like RHEL, EPEL and CentOS. Fedora might re-introduce parallell-installable stacks in the future (for example if a switch to a new Python version needs a transition period, or if enough interested maintainers somehow appear).
	Fedora does include alternate interpreter versions, e.g. `+python2.7+` or `+python3.5+`, but these are meant only for developers that need to test upstream code. Bug and security fixes for these interpreters only cover this use case. Packages such as `+pip+` or `+tox+`, which enable setting up isolated environments and installing third-party packages into them, MAY, as an exception to the rule above, use these interpreters as long as this is coordinated with the maintainers of the relevant Python interpreter.
	Naming	Nimeäminen
	Python packages have several different names, which should be kept in sync but will sometimes differ for historical or practical reasons. They are:
	the Fedora _source package name_ (or _component name_, `+%{name}+`),
	the Fedora _built RPM name_,
	the _project name_ used on https://pypi.org/[PyPI] or by https://pip.pypa.io[pip], and
	the _importable module name_ used in Python (a single package may have multiple importable modules).
	Some examples (both good and worse):
	\|Fedora component \|Built RPM \|Project name \|Importable module \|`+python-requests+` \|`+python3-requests+` \|`+requests+` \|`+requests+` \|`+python-django+` \|`+python3-django+` \|`+Django+` \|`+django+` \|`+PyYAML+` \|`+python3-pyyaml+` \|`+pyyaml+` \|`+yaml+` \|`+python-ldap+` \|`+python3-ldap+` \|`+python-ldap+` \|`+ldap+`, `+ldif+`, etc. \|`+python-pillow+` \|`+python3-pillow+` \|`+pillow+` \|`+PIL+` \|`+python-jupyter-client+` \|`+python3-jupyter-client+` \|`+jupyter-client+` \|`+jupyter_client+`
	Elsewhere in this text, the metavariables `+SRPMNAME+`, `+RPMNAME+`, `+PROJECTNAME+`, `+MODNAME+` refer to these names, respectively.
	Canonical project name
	Most of these names are case-sensitive machine-friendly identifiers, but the _project name_ has human-friendly semantics: it is case-insensitive and treats some sets of characters (like `+._-+`) specially. For automated use, it needs to be normalized to a canonical format used by Python tools and services such as setuptools, pip and PyPI. For example, the canonical name of the `+Django+` project is `+django+` (in lowercase). This normalization is defined in https://www.python.org/dev/peps/pep-0503/#normalized-names[PEP 503], and <<py_dist_name,the `+%{py_dist_name}+` macro>> implements it for Fedora packaging. The canonical name is obtained by switching the project name to lower case and converting all runs of non-alphanumeric characters to single “-” characters. Example: “The $$$ Tree” becomes “the-tree”.
	Elsewhere in this text, the metavariable `+DISTNAME+` refers to the canonical form of the project name.
	Note that in some places, the original, non-normalized project name must be used. For example, the <<pypi_source,`+%pypi_source+` macro>> and the `+%autosetup+` macro need `+Django+`, not `+django+`.
	Name limitations
	The character `pass:[+]` in names of built (i.e. non-SRPM) packages that include `+.dist-info+` or `+.egg-info+` directories is reserved for <<Extras>> and MUST NOT be used for any other purpose.
	As an exception, `pass:[+]` characters MAY appear at the _end_ of such names.

Loading…

copperi

Translation added

English

Finnish 10 characters edited Current translation

3 years ago

Browse all string changes

Things to check

Inconsistent

This string has more than one translation in this project or is untranslated in some components.

Reset

Glossary

English	Finnish
No related strings found in the glossary.

7074888 String information

Source string description

type: Title ==

Flags

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

Source string location

pages/Python.adoc:209

String age

3 years ago

Last updated

3 months ago

Source string age

4 years ago

Translation file

po/fi/master/pages/Python.po, string 38

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.