-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
5.4.0: pytest fails because missing test.support
#6
Comments
And other small issue is as well here that new/temporary directory added begore start build are breaking build (missing some bits in pyproject.toml) + /usr/bin/python3 -sBm build -w --no-isolation
* Getting build dependencies for wheel...
error: Multiple top-level packages discovered in a flat-layout: ['jaraco', 'SPECPARTS'].
To avoid accidental inclusion of unwanted files or directories,
setuptools will not proceed with this build.
If you are trying to create a single distribution with multiple packages
on purpose, you should not rely on automatic discovery.
Instead, consider the following options:
1. set up custom discovery (`find` directive with `include` or `exclude`)
2. use a `src-layout`
3. explicitly set `py_modules` or `packages` with a list of names
To find more information, look for "package discovery" on setuptools docs.
ERROR Backend subprocess exited when trying to invoke get_requires_for_build_wheel |
Gentle ping .. any update? |
We experience the same issue on nixpkgs, and importlib-resources 6.4.0 now relies on |
Per pytest-dev/pytest#12112 (comment)
https://docs.pytest.org/en/stable/reference/reference.html#confval-consider_namespace_packages |
Ah ha, but
And under pytest:
I've bisected this down to being introduced by pytest commit c85fce39b60a6cc3537e9da3e7a4f4946cfe4d49 |
It seems the problem is fixed by: 40a16ec It works fine for me now with pytest 8.2.0 and also the latest 8.3.2. A new release would be nice. |
Chasing down the pytest commit that fixes this, which I think is pytest-dev/pytest#12208 , we may have to wait until pytest 8.4.0 is released. |
Anyone have ideas why this is also occurring in I have tried 40a16ec, but for
|
Apologies for the radio silence. I only visit my projects incidentally and don't subscribe to email notifications for filed issues, so feel free to ping me if something is languishing that needs my attention.
This issue is being tracked in jaraco/skeleton#116.
The test suite is usable. It's very rare that I'll release one of my projects if the tests aren't passing in CI.
A new release is cut (v5.5.0). Let me know if that doesn't at least work around this issue. |
I've lost track, but there were lots of changes around module discovery in 8.0, 8.1, and 8.2, so I'd not be surprised if some or all projects are actually now reliant on pytest 8.x or even 8.2. |
I'm not sure but on first look looks lik eon file is missing in tests/
The text was updated successfully, but these errors were encountered: