rpms/pyproject-rpm-macros
7
0
Fork 0
Code Issues Pull Requests Releases Activity

Fix two misspellings of “requirements,” one user-visible

Browse Source
This commit is contained in:
Benjamin A. Beasley 2021-07-25 17:35:52 -04:00
parent 5169e0e340
commit 6ee7a6baea
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
pyproject_buildrequires.py
View File

@ -342,7 +342,7 @@ def generate_requires(
for req_file in requirement_files: for req_file in requirement_files:
requirements.extend( requirements.extend(
convert_requirements_txt(req_file, pathlib.Path(req_file.name)), convert_requirements_txt(req_file, pathlib.Path(req_file.name)),
source=f'requirments file {req_file.name}' source=f'requirements file {req_file.name}'
) )
requirements.check(source='all requirement files') requirements.check(source='all requirement files')
if use_build_system: if use_build_system:

2
pyproject_requirements_txt.py
View File

@ -20,7 +20,7 @@ PKGNAME_RE = re.compile(r'^[-_a-zA-Z0-9]+')
def convert_requirements_txt(lines, path:Path = None): def convert_requirements_txt(lines, path:Path = None):
"""Convert lines of a requirements file to PEP 440-style requirement strs """Convert lines of a requirements file to PEP 440-style requirement strs
This does NOT handle all of requitrements.txt features (only pip can do This does NOT handle all of requirements.txt features (only pip can do
that), but tries its best. that), but tries its best.
The resulting requirements might not actually be valid (either because The resulting requirements might not actually be valid (either because