Lib.rs

Cargo Features

pep508_rs has no features set by default.

[dependencies]
pep508_rs = { version = "0.5.0", features = ["pyo3", "rkyv", "serde", "tracing", "non-pep508-extensions", "serde_json"] }

pyo3 = pyo3-log, tracing

Enables pyo3, pyo3 of pep440_rs, log of tracing

Affects pep508_rs::python_module…

rkyv

Enables rkyv, rkyv of pep440_rs

serde

Enables serde, serde of pep440_rs, serde of url

tracing pyo3?

Enables tracing, tracing of pep440_rs

non-pep508-extensions

PEP 508 allows only URLs such as foo @ https://example.org/foo or foo @ file:///home/ferris/foo, and arguably does not allow relative paths in file URLs (foo @ file://./foo, foo @ file:foo-3.0.0-py3-none-any.whl, foo @ file://foo-3.0.0-py3-none-any.whl), as they are not part of the relevant RFCs, even though widely supported. Pip accepts relative file URLs and paths instead of urls (foo @ ./foo-3.0.0-py3-none-any.whl). The non-pep508-features controls whether these non-spec features will be supported.

Features from optional dependencies

In crates that don't use the dep: syntax, optional dependencies automatically become Cargo features. These features may have been created by mistake, and this functionality may be removed in the future.

pyo3-log pyo3?

serde_json implicit feature

Enables serde_json

serde_json:

A JSON serialization file format