Clarify purelib vs platlib in PEP 427
This commit is contained in:
parent
805a0ab6a1
commit
2e47d2bdaa
11
pep-0427.txt
11
pep-0427.txt
|
@ -367,18 +367,19 @@ Why does wheel also allow S/MIME signatures?
|
||||||
update system. Wheel only provides the building block.
|
update system. Wheel only provides the building block.
|
||||||
|
|
||||||
What's the deal with "purelib" vs. "platlib"?
|
What's the deal with "purelib" vs. "platlib"?
|
||||||
Wheel preserves the historic "purelib" vs. "platlib" distinction
|
Wheel preserves the "purelib" vs. "platlib" distinction, which is
|
||||||
even though both map to the same install location in any system the
|
significant on some platforms. For example, Fedora installs pure
|
||||||
author could find.
|
Python packages to '/usr/lib/pythonX.Y/site-packages' and platform
|
||||||
|
dependent packages to '/usr/lib64/pythonX.Y/site-packages'.
|
||||||
|
|
||||||
For example, a wheel with "Root-Is-Purelib: false" with all its files
|
A wheel with "Root-Is-Purelib: false" with all its files
|
||||||
in ``{name}-{version}.data/purelib`` is equivalent to a wheel with
|
in ``{name}-{version}.data/purelib`` is equivalent to a wheel with
|
||||||
"Root-Is-Purelib: true" with those same files in the root, and it
|
"Root-Is-Purelib: true" with those same files in the root, and it
|
||||||
is legal to have files in both the "purelib" and "platlib" categories.
|
is legal to have files in both the "purelib" and "platlib" categories.
|
||||||
|
|
||||||
In practice a wheel should have only one of "purelib" or "platlib"
|
In practice a wheel should have only one of "purelib" or "platlib"
|
||||||
depending on whether it is pure Python or not and those files should
|
depending on whether it is pure Python or not and those files should
|
||||||
be at the root.
|
be at the root with the appropriate setting given for "Root-is-purelib".
|
||||||
|
|
||||||
References
|
References
|
||||||
==========
|
==========
|
||||||
|
|
Loading…
Reference in New Issue