Skip to content

Instantly share code, notes, and snippets.

@davipatti

davipatti/build-log.txt

Created January 16, 2026 20:20
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save davipatti/a5cac77d857cd65e9966b3078f752770 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save davipatti/a5cac77d857cd65e9966b3078f752770 to your computer and use it in GitHub Desktop.
Download ZIP
limix-legacy build log
Raw
build-log.txt
Resolved 68 packages in 2ms
Building limix-legacy @ git+https://github.com/davipatti/limix-legacy@3636e3d420750a8af5fad27e849122d3068ef459
× Failed to build `limix-legacy @ git+https://github.com/davipatti/limix-legacy@3636e3d420750a8af5fad27e849122d3068ef459`
├─▶ The build backend returned an error
╰─▶ Call to `setuptools.build_meta.build_wheel` failed (exit status: 1)
[stdout]
running bdist_wheel
running build
running build_py
copying limix_legacy/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy
running egg_info
writing limix_legacy.egg-info/PKG-INFO
writing dependency_links to limix_legacy.egg-info/dependency_links.txt
writing requirements to limix_legacy.egg-info/requires.txt
writing top-level names to limix_legacy.egg-info/top_level.txt
reading manifest file 'limix_legacy.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'limix_legacy.egg-info/SOURCES.txt'
copying limix_legacy/deprecated/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated
copying limix_legacy/deprecated/core.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated
copying limix_legacy/deprecated/io/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/io
copying limix_legacy/deprecated/io/conversion.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/io
copying limix_legacy/deprecated/io/data.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/io
copying limix_legacy/deprecated/io/data_util.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/io
copying limix_legacy/deprecated/io/genotype_reader.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/io
copying limix_legacy/deprecated/io/output_writer.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/io
copying limix_legacy/deprecated/io/phenotype_reader.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/io
copying limix_legacy/deprecated/io/plink.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/io
copying limix_legacy/deprecated/modules/BLUP.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/dirIndirVD_commented_forDistrib.py ->
build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/grm.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/lmm_fast.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/lmm_forest.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/lmmlasso.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/mixedForestUtils.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/multiPanama.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/panama.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/parMixedForest.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/pySplittingCore.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/qtl.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/social_data_HSmice_paper.py ->
build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/varDecompSet.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/modules/varianceDecomposition.py ->
build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/modules
copying limix_legacy/deprecated/stats/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/stats
copying limix_legacy/deprecated/stats/fdr.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/stats
copying limix_legacy/deprecated/stats/geno_summary.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/stats
copying limix_legacy/deprecated/stats/pca.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/stats
copying limix_legacy/deprecated/stats/power.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/stats
copying limix_legacy/deprecated/utils/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/utils
copying limix_legacy/deprecated/utils/fastlmm.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/utils
copying limix_legacy/deprecated/utils/plot.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/utils
copying limix_legacy/deprecated/utils/preprocess.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/deprecated/utils
copying limix_legacy/ensemble/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/ensemble
copying limix_legacy/ensemble/blup.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/ensemble
copying limix_legacy/ensemble/lmm_fast.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/ensemble
copying limix_legacy/ensemble/lmm_forest.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/ensemble
copying limix_legacy/ensemble/lmm_forest_utils.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/ensemble
copying limix_legacy/ensemble/par_lmm_forest.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/ensemble
copying limix_legacy/ensemble/py_splitting_core.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/ensemble
copying limix_legacy/io/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/io
copying limix_legacy/io/conversion.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/io
copying limix_legacy/io/data.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/io
copying limix_legacy/io/data_util.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/io
copying limix_legacy/io/genotype_reader.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/io
copying limix_legacy/io/output_writer.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/io
copying limix_legacy/io/phenotype_reader.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/io
copying limix_legacy/io/plink.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/io
copying limix_legacy/stats/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/stats
copying limix_legacy/stats/geno_summary.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/stats
copying limix_legacy/stats/power.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/stats
copying limix_legacy/test/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test
copying limix_legacy/test/data.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test
copying limix_legacy/test/test_modules.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test
copying limix_legacy/test/covar/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/covar
copying limix_legacy/test/covar/covar.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/covar
copying limix_legacy/test/covar/test_combinators.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/covar
copying limix_legacy/test/covar/test_freeform.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/covar
copying limix_legacy/test/covar/test_lik.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/covar
copying limix_legacy/test/covar/test_linear.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/covar
copying limix_legacy/test/covar/test_se.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/covar
copying limix_legacy/test/gp/test_gp.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/gp
copying limix_legacy/test/gp/test_gplvm.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/gp
copying limix_legacy/test/lmm/test_CInteractLMM.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm
copying limix_legacy/test/lmm/test_CKroneckerLMM.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm
copying limix_legacy/test/lmm/test_CLMM.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm
copying limix_legacy/test/lmm/test_CLMM_large.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm
copying limix_legacy/test/lmm/lmm_data1/Beta.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm/lmm_data1
copying limix_legacy/test/lmm/lmm_data1/BetaSte.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm/lmm_data1
copying limix_legacy/test/lmm/lmm_data1/Cov.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm/lmm_data1
copying limix_legacy/test/lmm/lmm_data1/K.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm/lmm_data1
copying limix_legacy/test/lmm/lmm_data1/X.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm/lmm_data1
copying limix_legacy/test/lmm/lmm_data1/Y.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm/lmm_data1
copying limix_legacy/test/lmm/lmm_data1/pv.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm/lmm_data1
copying limix_legacy/test/lmm_forest/test_lmm_forest.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_forest
copying limix_legacy/test/lmm_forest/test_data/lmm_forest_toy_data.h5 ->
build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_forest/test_data
copying limix_legacy/test/lmm_lasso/test_lmmlasso.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_lasso
copying limix_legacy/test/lmm_lasso/lmmlasso/K.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_lasso/lmmlasso
copying limix_legacy/test/lmm_lasso/lmmlasso/X.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_lasso/lmmlasso
copying limix_legacy/test/lmm_lasso/lmmlasso/causal_idx.txt ->
build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_lasso/lmmlasso
copying limix_legacy/test/lmm_lasso/lmmlasso/params_true.txt ->
build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_lasso/lmmlasso
copying limix_legacy/test/lmm_lasso/lmmlasso/y.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_lasso/lmmlasso
copying limix_legacy/test/lmm_lasso/lmmlasso/yhat.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/lmm_lasso/lmmlasso
copying limix_legacy/test/varDecomp/test_varDecomp.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/varDecomp
copying limix_legacy/test/varDecomp/varDecomp/X.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/varDecomp/varDecomp
copying limix_legacy/test/varDecomp/varDecomp/Y.txt -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/varDecomp/varDecomp
copying limix_legacy/test/varDecomp/varDecomp/params_true.txt ->
build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/test/varDecomp/varDecomp
copying limix_legacy/utils/__init__.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
copying limix_legacy/utils/check_grad.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
copying limix_legacy/utils/eigen.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
copying limix_legacy/utils/linalg.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
copying limix_legacy/utils/plot.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
copying limix_legacy/utils/preprocess.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
copying limix_legacy/utils/psd_solve.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
copying limix_legacy/utils/svd_utils.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
copying limix_legacy/utils/util_functions.py -> build/lib.macosx-15.0-arm64-cpython-311/limix_legacy/utils
running build_ext
[stderr]
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:82:
SetuptoolsDeprecationWarning: `project.license` as a TOML table is deprecated
!!
********************************************************************************
Please use a simple string containing a SPDX expression for `project.license`. You can also use `project.license-files`. (Both
options available on setuptools>=77.0.0).
By 2026-Feb-18, you need to update your project and remove deprecated calls
or your builds will no longer be supported.
See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
********************************************************************************
!!
corresp(dist, value, root_dir)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:82:
SetuptoolsWarning: `install_requires` overwritten in `pyproject.toml` (dependencies)
corresp(dist, value, root_dir)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:61:
SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!
********************************************************************************
Please consider removing the following classifiers in favor of a SPDX license expression:
License :: OSI Approved :: Apache Software License
See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
********************************************************************************
!!
dist._finalize_license_expression()
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning:
License classifiers are deprecated.
!!
********************************************************************************
Please consider removing the following classifiers in favor of a SPDX license expression:
License :: OSI Approved :: Apache Software License
See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
********************************************************************************
!!
self._finalize_license_expression()
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.deprecated' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.deprecated' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.deprecated' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.deprecated' to be distributed and are
already explicitly excluding 'limix_legacy.deprecated' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.deprecated.io' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.deprecated.io' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.deprecated.io' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.deprecated.io' to be distributed and are
already explicitly excluding 'limix_legacy.deprecated.io' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.deprecated.modules' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.deprecated.modules' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.deprecated.modules' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.deprecated.modules' to be distributed and are
already explicitly excluding 'limix_legacy.deprecated.modules' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.deprecated.stats' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.deprecated.stats' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.deprecated.stats' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.deprecated.stats' to be distributed and are
already explicitly excluding 'limix_legacy.deprecated.stats' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.deprecated.utils' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.deprecated.utils' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.deprecated.utils' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.deprecated.utils' to be distributed and are
already explicitly excluding 'limix_legacy.deprecated.utils' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.ensemble' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.ensemble' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.ensemble' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.ensemble' to be distributed and are
already explicitly excluding 'limix_legacy.ensemble' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.io' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.io' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.io' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.io' to be distributed and are
already explicitly excluding 'limix_legacy.io' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.stats' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.stats' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.stats' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.stats' to be distributed and are
already explicitly excluding 'limix_legacy.stats' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test' to be distributed and are
already explicitly excluding 'limix_legacy.test' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.covar' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.covar' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.covar' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.covar' to be distributed and are
already explicitly excluding 'limix_legacy.test.covar' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.gp' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.gp' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.gp' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.gp' to be distributed and are
already explicitly excluding 'limix_legacy.test.gp' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.lmm' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.lmm' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.lmm' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.lmm' to be distributed and are
already explicitly excluding 'limix_legacy.test.lmm' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.lmm.lmm_data1' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.lmm.lmm_data1' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.lmm.lmm_data1' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.lmm.lmm_data1' to be distributed and are
already explicitly excluding 'limix_legacy.test.lmm.lmm_data1' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.lmm_forest' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.lmm_forest' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.lmm_forest' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.lmm_forest' to be distributed and are
already explicitly excluding 'limix_legacy.test.lmm_forest' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.lmm_forest.test_data' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.lmm_forest.test_data' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.lmm_forest.test_data' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.lmm_forest.test_data' to be distributed and are
already explicitly excluding 'limix_legacy.test.lmm_forest.test_data' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.lmm_lasso' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.lmm_lasso' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.lmm_lasso' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.lmm_lasso' to be distributed and are
already explicitly excluding 'limix_legacy.test.lmm_lasso' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.lmm_lasso.lmmlasso' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.lmm_lasso.lmmlasso' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.lmm_lasso.lmmlasso' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.lmm_lasso.lmmlasso' to be distributed and are
already explicitly excluding 'limix_legacy.test.lmm_lasso.lmmlasso' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.varDecomp' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.varDecomp' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.varDecomp' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.varDecomp' to be distributed and are
already explicitly excluding 'limix_legacy.test.varDecomp' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.test.varDecomp.varDecomp' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.test.varDecomp.varDecomp' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.test.varDecomp.varDecomp' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.test.varDecomp.varDecomp' to be distributed and are
already explicitly excluding 'limix_legacy.test.varDecomp.varDecomp' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/build_py.py:212: _Warning: Package
'limix_legacy.utils' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'limix_legacy.utils' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'limix_legacy.utils' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'limix_legacy.utils' to be distributed and are
already explicitly excluding 'limix_legacy.utils' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
Traceback (most recent call last):
File "<string>", line 11, in <module>
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/build_meta.py", line 432, in
build_wheel
return _build(['bdist_wheel'])
^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/build_meta.py", line 423, in _build
return self._build_with_temp_dir(
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/build_meta.py", line 404, in
_build_with_temp_dir
self.run_setup()
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/build_meta.py", line 317, in run_setup
exec(code, locals())
File "<string>", line 238, in <module>
File "<string>", line 221, in setup_package
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/__init__.py", line 115, in setup
return distutils.core.setup(**attrs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 186, in
setup
return run_commands(dist)
^^^^^^^^^^^^^^^^^^
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/core.py", line 202, in
run_commands
dist.run_commands()
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 1002, in
run_commands
self.run_command(cmd)
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/dist.py", line 1102, in run_command
super().run_command(command)
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 1021, in
run_command
cmd_obj.run()
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/command/bdist_wheel.py", line 370,
in run
self.run_command("build")
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/cmd.py", line 357, in
run_command
self.distribution.run_command(command)
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/dist.py", line 1102, in run_command
super().run_command(command)
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 1021, in
run_command
cmd_obj.run()
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/command/build.py", line
135, in run
self.run_command(cmd_name)
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/cmd.py", line 357, in
run_command
self.distribution.run_command(command)
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/dist.py", line 1102, in run_command
super().run_command(command)
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/dist.py", line 1021, in
run_command
cmd_obj.run()
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/Cython/Distutils/old_build_ext.py", line 186,
in run
_build_ext.build_ext.run(self)
File "/Users/pattinson/.cache/uv/builds-v0/.tmpy899K1/lib/python3.11/site-packages/setuptools/_distutils/command/build_ext.py", line
368, in run
self.build_extensions()
File "<string>", line 51, in build_extensions
ValueError: not enough values to unpack (expected 2, got 1)
hint: This usually indicates a problem with the package or the build environment.
help: `limix-legacy` was included because `mapdeduce` (v2.0.0) depends on `limix-legacy`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment