Closed kloczek closed 2 months ago
As per pyproject.toml
:
requires-python = ">= 3.9"
I would be happy to get a patch for Python 3.8, given that it remains in support for over a year from now.
If it is only matter of use python 3>=3.9 than OK .. don't worry and feel free to close this ticket because I'm now in the process of moving to python 3.9 😋 Thank you 👍
Thanks, @kloczek, I'll keep the issue open for now in case anyone else runs into it.
BTW looks like some bits are missing in pyproject.toml. I've accidentally created temporary directory and than build failed. Here is test case:
From the error message, this looks like things are working as intended: the package uses automatic discovery, and creating a temporary directory breaks that.
Yes exactly and it is really hard to find modules which uses auto discovery. I have +1.2k packaged python modules and in mean time I made the test on all ow them and found that only 4 are affected by this kind of issue.
I don't think it's really an issue; on the contrary it's good that this package is simple enough that I can just rely on the defaults and avoid unnecessary extra configuration. It's increasingly uncommon to modify source directories, building out-of-tree is increasingly common, and in this case the error message was clear and obvious, so I don't think there's a problem.
Closing this issue, as Python 3.8 is nearly EOL and I'm not going to support it now.
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulescut off from access to the public network
(pytest is executed with-m "not network"
)Here is pytest output:
Here is list of installed modules in build env