290941c5f3
The PEP 517 shows an example backend-path like this:
[build-system]
# Defined by PEP 518:
requires = ["flit"]
# Defined by this PEP:
build-backend = "local_backend"
backend-path = ["backend"]
https://www.python.org/dev/peps/pep-0517/#source-trees
See that backend-path is a list. Our code previously only supported string path.
Obviously a string path is wrong, but we keep it to support projects that have
made the mistake, such as flit-core.
Add a small integration test for both cases.
Note that the new spec files deliberately don't do much, to save CI time.
46 lines
813 B
RPMSpec
46 lines
813 B
RPMSpec
Name: python-poetry-core
|
|
Version: 1.0.0
|
|
Release: 0%{?dist}
|
|
Summary: Poetry PEP 517 Build Backend
|
|
|
|
License: MIT
|
|
URL: https://pypi.org/project/poetry-core/
|
|
Source0: %{pypi_source poetry-core}
|
|
|
|
BuildArch: noarch
|
|
BuildRequires: python3-devel
|
|
BuildRequires: pyproject-rpm-macros
|
|
|
|
%description
|
|
Test a build with pyproject.toml backend-path = [.]
|
|
poetry-core builds with poetry-core.
|
|
|
|
|
|
%package -n python3-poetry-core
|
|
Summary: %{summary}
|
|
|
|
%description -n python3-poetry-core
|
|
...
|
|
|
|
|
|
%prep
|
|
%autosetup -p1 -n poetry-core-%{version}
|
|
|
|
|
|
%generate_buildrequires
|
|
%pyproject_buildrequires
|
|
|
|
|
|
%build
|
|
%pyproject_wheel
|
|
|
|
|
|
%install
|
|
%pyproject_install
|
|
%pyproject_save_files poetry
|
|
|
|
|
|
%files -n python3-poetry-core -f %{pyproject_files}
|
|
%doc README.md
|
|
%license LICENSE
|