Next: , Previous: , Up: 打包指导   [Contents][Index]

22.4.7 Python模块

我们目前为Python 2和Python 3打包,如版本号的规则所述,它们的Scheme变量名分别是python-2python。为了避免和其他编程语言的冲突,Python模块的软件包名字最好含有python

Some modules are compatible with only one version of Python, others with both. If the package Foo is compiled with Python 3, we name it python-foo. If it is compiled with Python 2, we name it python2-foo. Packages should be added when they are necessary; we don’t add Python 2 variants of the package unless we are going to use them.

如果一个项目的名字已经含有python这个单词,我们把它丢掉;例如,python-dateutil模块打包后的名字是python-dateutilpython2-dateutil。如果项目的名字以py开头(如 pytz),我们把它保留,并且添加上面所述的前缀。

注: Currently there are two different build systems for Python packages in Guix: python-build-system and pyproject-build-system. For the longest time, Python packages were built from an informally specified file. That worked amazingly well, considering Python’s success, but was difficult to build tooling around. As a result, a host of alternative build systems emerged and the community eventually settled on a formal standard for specifying build requirements. pyproject-build-system is Guix’s implementation of this standard. It is considered “experimental” in that it does not yet support all the various PEP-517 build backends, but you are encouraged to try it for new Python packages and report any problems. It will eventually be deprecated and merged into python-build-system. 指定依赖

Dependency information for Python packages is usually available in the package source tree, with varying degrees of accuracy: in the pyproject.toml file, the file, in requirements.txt, or in tox.ini (the latter mostly for test dependencies).

你在写软件包配方时的任务是把这些依赖转换成相应的“输入”(see inputs)。尽管pypi导入工具通常可以做得很好(see 调用guix import),你可能想检查下面这个清单,以决定每个依赖放在哪儿。

Next: , Previous: , Up: 打包指导   [Contents][Index]