-
Notifications
You must be signed in to change notification settings - Fork 55
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.9.3] problem observe during the Debian packaging #1083
Comments
I am not using it. PyMca should build fine with I guess Debian needs it in order to split the package into data, documentation and so on, but PyMca does not use setuptools. |
[build-system]
requires = [
"setuptools",
"wheel",
"oldest-supported-numpy; python_version< '3.9'",
"numpy >= 2.0.0; python_version >= '3.9'",
"Cython"
]
build-backend = "setuptools.build_meta"
yes you are using setuptools ;), I will try to build only from this and see what is going one.
thanks
Fred
|
Hello after removing the setup.py, I try to build and got this.
```
$ python -m build
* Creating isolated environment: venv+pip...
* Installing packages in isolated environment:
- Cython
- numpy >= 2.0.0; python_version >= '3.9'
- oldest-supported-numpy; python_version< '3.9'
- setuptools
- wheel
* Getting build dependencies for sdist...
error: Multiple top-level packages discovered in a flat-layout: ['icons', 'PyMca5', 'package'].
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_sdist
```
|
Ok. I do not think you can avoid it for the time being then. I thought i was not using setuptools because python 3.12 was explicitly preventing the call to setup.py. I do not think you can avoid using setup.py then (for the time being). I have checked matplotlib, and they still have setuptools in pyproject.toml https://github.com/matplotlib/matplotlib/blob/main/pyproject.toml |
the problem with Python3.12 is about distutils not setuptools. :)
I agreed thaht I need setup.py until the full integration is done in pyproject.toml or setup.cfg
Cheers
Fred
|
The doc should compile now. I have been able to reproduce the warning and correct it in #1084 with a recent sphinx. I have used the command below to generate the documentation:
|
Hello Armando.
here my remarks for htis version of PyMca :))
thanks a lot
it stops the compilation of the doc
At some point getting rid of the setup.py will become mandatory
The text was updated successfully, but these errors were encountered: