package/python-aiofiles: migrate to hatchling pep517 build backend
When building with a pep517 frontend we need to use the specified build backend as opposed to the fallback setuptools build which only works when not building with a pep517 frontend. Fixes: ERROR Backend 'hatchling.build' is not available. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
This commit is contained in:
parent
3c0c08e80f
commit
05f315c83b
@ -7,8 +7,9 @@
|
||||
PYTHON_AIOFILES_VERSION = 23.2.1
|
||||
PYTHON_AIOFILES_SOURCE = aiofiles-$(PYTHON_AIOFILES_VERSION).tar.gz
|
||||
PYTHON_AIOFILES_SITE = https://files.pythonhosted.org/packages/af/41/cfed10bc64d774f497a86e5ede9248e1d062db675504b41c320954d99641
|
||||
PYTHON_AIOFILES_SETUP_TYPE = setuptools
|
||||
PYTHON_AIOFILES_SETUP_TYPE = pep517
|
||||
PYTHON_AIOFILES_LICENSE = Apache-2.0
|
||||
PYTHON_AIOFILES_LICENSE_FILES = LICENSE
|
||||
PYTHON_AIOFILES_DEPENDENCIES = host-python-hatchling
|
||||
|
||||
$(eval $(python-package))
|
||||
|
Loading…
Reference in New Issue
Block a user