(vnpy40env) [root@localhost vnpy40env]# pip3.13 install vnpy-mini -i https://pypi.vnpy.com
Looking in indexes: https://pypi.vnpy.com
Collecting vnpy-mini
Downloading https://pypi.vnpy.com/packages/vnpy_mini-1.6.3.1.tar.gz (3.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.2/3.2 MB 5.2 MB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting importlib_metadata (from vnpy-mini)
Downloading https://pypi.vnpy.com/packages/importlib_metadata-8.7.0-py3-none-any.whl (27 kB)
Collecting zipp>=3.20 (from importlib_metadata->vnpy-mini)
Downloading https://pypi.vnpy.com/packages/zipp-3.23.0-py3-none-any.whl (10 kB)
Building wheels for collected packages: vnpy-mini
Building wheel for vnpy-mini (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for vnpy-mini (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [534 lines of output]
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/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 :: MIT License
See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
********************************************************************************
!!
self._finalize_license_expression()
running bdist_wheel
running build
running build_py
creating build/lib.linux-x86_64-cpython-313/vnpy_mini
copying vnpy_mini/__init__.py -> build/lib.linux-x86_64-cpython-313/vnpy_mini
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api
copying vnpy_mini/api/__init__.py -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api
copying vnpy_mini/api/mini_constant.py -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/gateway
copying vnpy_mini/gateway/__init__.py -> build/lib.linux-x86_64-cpython-313/vnpy_mini/gateway
copying vnpy_mini/gateway/mini_gateway.py -> build/lib.linux-x86_64-cpython-313/vnpy_mini/gateway
running egg_info
writing vnpy_mini.egg-info/PKG-INFO
writing dependency_links to vnpy_mini.egg-info/dependency_links.txt
writing requirements to vnpy_mini.egg-info/requires.txt
writing top-level names to vnpy_mini.egg-info/top_level.txt
reading manifest file 'vnpy_mini.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
writing manifest file 'vnpy_mini.egg-info/SOURCES.txt'
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'vnpy_mini.api.generator' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_mini.api.generator' 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 'vnpy_mini.api.generator' 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 'vnpy_mini.api.generator' to be distributed and are
already explicitly excluding 'vnpy_mini.api.generator' 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)
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'vnpy_mini.api.include.mini' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_mini.api.include.mini' 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 'vnpy_mini.api.include.mini' 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 'vnpy_mini.api.include.mini' to be distributed and are
already explicitly excluding 'vnpy_mini.api.include.mini' 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)
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'vnpy_mini.api.include.pybind11' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_mini.api.include.pybind11' 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 'vnpy_mini.api.include.pybind11' 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 'vnpy_mini.api.include.pybind11' to be distributed and are
already explicitly excluding 'vnpy_mini.api.include.pybind11' 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)
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'vnpy_mini.api.include.pybind11.detail' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_mini.api.include.pybind11.detail' 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 'vnpy_mini.api.include.pybind11.detail' 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 'vnpy_mini.api.include.pybind11.detail' to be distributed and are
already explicitly excluding 'vnpy_mini.api.include.pybind11.detail' 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)
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'vnpy_mini.api.libs' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_mini.api.libs' 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 'vnpy_mini.api.libs' 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 'vnpy_mini.api.libs' to be distributed and are
already explicitly excluding 'vnpy_mini.api.libs' 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)
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'vnpy_mini.api.vnmini' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_mini.api.vnmini' 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 'vnpy_mini.api.vnmini' 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 'vnpy_mini.api.vnmini' to be distributed and are
already explicitly excluding 'vnpy_mini.api.vnmini' 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)
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'vnpy_mini.api.vnmini.vnminimd' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_mini.api.vnmini.vnminimd' 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 'vnpy_mini.api.vnmini.vnminimd' 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 'vnpy_mini.api.vnmini.vnminimd' to be distributed and are
already explicitly excluding 'vnpy_mini.api.vnmini.vnminimd' 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)
/tmp/pip-build-env-_x2ze08a/overlay/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'vnpy_mini.api.vnmini.vnminitd' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'vnpy_mini.api.vnmini.vnminitd' 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 'vnpy_mini.api.vnmini.vnminitd' 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 'vnpy_mini.api.vnmini.vnminitd' to be distributed and are
already explicitly excluding 'vnpy_mini.api.vnmini.vnminitd' 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)
copying vnpy_mini/api/libthostmduserapi.so -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api
copying vnpy_mini/api/libthosttraderapi.so -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api
copying vnpy_mini/api/thostmduserapi.dll -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api
copying vnpy_mini/api/thosttraderapi.dll -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_header_define.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_header_function.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_header_on.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_header_process.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_source_function.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_source_module.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_source_on.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_source_process.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_source_switch.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_md_source_task.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_header_define.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_header_function.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_header_on.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_header_process.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_source_function.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_source_module.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_source_on.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_source_process.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_source_switch.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
copying vnpy_mini/api/generator/mini_td_source_task.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/generator
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/mini
copying vnpy_mini/api/include/mini/ThostFtdcMdApi.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/mini
copying vnpy_mini/api/include/mini/ThostFtdcTraderApi.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/mini
copying vnpy_mini/api/include/mini/ThostFtdcUserApiDataType.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/mini
copying vnpy_mini/api/include/mini/ThostFtdcUserApiStruct.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/mini
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/attr.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/buffer_info.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/cast.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/chrono.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/common.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/complex.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/eigen.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/embed.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/eval.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/functional.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/iostream.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/numpy.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/operators.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/options.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/pybind11.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/pytypes.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/stl.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
copying vnpy_mini/api/include/pybind11/stl_bind.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11/detail
copying vnpy_mini/api/include/pybind11/detail/class.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11/detail
copying vnpy_mini/api/include/pybind11/detail/common.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11/detail
copying vnpy_mini/api/include/pybind11/detail/descr.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11/detail
copying vnpy_mini/api/include/pybind11/detail/init.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11/detail
copying vnpy_mini/api/include/pybind11/detail/internals.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11/detail
copying vnpy_mini/api/include/pybind11/detail/typeid.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/include/pybind11/detail
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api/libs
copying vnpy_mini/api/libs/thostmduserapi.lib -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/libs
copying vnpy_mini/api/libs/thosttraderapi.lib -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/libs
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini
copying vnpy_mini/api/vnmini/vnmini.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/dllmain.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/framework.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/pch.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/pch.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/stdafx.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/stdafx.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/targetver.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/vnminimd.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
copying vnpy_mini/api/vnmini/vnminimd/vnminimd.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminimd
creating build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/dllmain.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/framework.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/pch.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/pch.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/stdafx.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/stdafx.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/targetver.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/vnminitd.cpp -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
copying vnpy_mini/api/vnmini/vnminitd/vnminitd.h -> build/lib.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
running build_ext
building 'vnpy_mini.api.vnminitd' extension
creating build/temp.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd
g++ -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -fPIC -Ivnpy_mini/api/include -Ivnpy_mini/api/vnmini -I/root/vnpy40env/vnpy40env/include -I/usr/local/include/python3.13 -c vnpy_mini/api/vnmini/vnminitd/vnminitd.cpp -o build/temp.linux-x86_64-cpython-313/vnpy_mini/api/vnmini/vnminitd/vnminitd.o -std=c++17 -O3 -Wno-delete-incomplete -Wno-sign-compare
包含于文件 vnpy_mini/api/include/pybind11/cast.h:16,
于 vnpy_mini/api/include/pybind11/attr.h:13,
于 vnpy_mini/api/include/pybind11/pybind11.h:43,
于 vnpy_mini/api/vnmini/vnmini.h:10,
于 vnpy_mini/api/vnmini/vnminitd/vnminitd.h:6,
于 vnpy_mini/api/vnmini/vnminitd/vnminitd.cpp:4:
vnpy_mini/api/include/pybind11/detail/internals.h: 在函数‘pybind11::detail::internals& pybind11::detail::get_internals()’中:
vnpy_mini/api/include/pybind11/detail/internals.h:194:27: 警告：‘void PyEval_InitThreads()’ 已被弃用 [-Wdeprecated-declarations]
194 | PyEval_InitThreads();
| ~~~~~~~~~~~~~~~~~~^~
包含于文件 /usr/local/include/python3.13/Python.h:124,
于 vnpy_mini/api/include/pybind11/detail/common.h:112,
于 vnpy_mini/api/include/pybind11/pytypes.h:12,
于 vnpy_mini/api/include/pybind11/cast.h:13:
/usr/local/include/python3.13/ceval.h:114:37: 附注：在此声明
114 | Py_DEPRECATED(3.9) PyAPI_FUNC(void) PyEval_InitThreads(void);
| ^~~~~~~~~~~~~~~~~~
vnpy_mini/api/include/pybind11/cast.h: 在函数‘std::string pybind11::detail::error_string()’中:
vnpy_mini/api/include/pybind11/cast.h:441:36: 错误：对不完全的类型‘PyFrameObject’ {aka ‘struct _frame’}的非法使用
441 | " " + handle(frame->f_code->co_filename).cast<std::string>() +
| ^~
包含于文件 /usr/local/include/python3.13/Python.h:67:
/usr/local/include/python3.13/pytypedefs.h:22:16: 附注：forward declaration of ‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
| ^~~~~~
vnpy_mini/api/include/pybind11/cast.h:441:75: 错误：expected primary-expression before ‘>’ token
441 | " " + handle(frame->f_code->co_filename).cast<std::string>() +
| ^
vnpy_mini/api/include/pybind11/cast.h:441:77: 错误：expected primary-expression before ‘)’ token
441 | " " + handle(frame->f_code->co_filename).cast<std::string>() +
| ^
vnpy_mini/api/include/pybind11/cast.h:443:29: 错误：对不完全的类型‘PyFrameObject’ {aka ‘struct _frame’}的非法使用
443 | handle(frame->f_code->co_name).cast<std::string>() + "\n";
| ^~
/usr/local/include/python3.13/pytypedefs.h:22:16: 附注：forward declaration of ‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
| ^~~~~~
vnpy_mini/api/include/pybind11/cast.h:443:64: 错误：expected primary-expression before ‘>’ token
443 | handle(frame->f_code->co_name).cast<std::string>() + "\n";
| ^
vnpy_mini/api/include/pybind11/cast.h:443:66: 错误：expected primary-expression before ‘)’ token
443 | handle(frame->f_code->co_name).cast<std::string>() + "\n";
| ^
vnpy_mini/api/include/pybind11/cast.h:444:26: 错误：对不完全的类型‘PyFrameObject’ {aka ‘struct _frame’}的非法使用
444 | frame = frame->f_back;
| ^~
/usr/local/include/python3.13/pytypedefs.h:22:16: 附注：forward declaration of ‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
| ^~~~~~
vnpy_mini/api/include/pybind11/pybind11.h: 在函数‘pybind11::function pybind11::get_type_overload(const void*, const detail::type_info*, const char*)’中:
vnpy_mini/api/include/pybind11/pybind11.h:1890:49: 错误：‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘frame’
1890 | PyFrameObject *frame = PyThreadState_Get()->frame;
| ^~~~~
vnpy_mini/api/include/pybind11/pybind11.h:1891:41: 错误：对不完全的类型‘PyFrameObject’ {aka ‘struct _frame’}的非法使用
1891 | if (frame && (std::string) str(frame->f_code->co_name) == name &&
| ^~
/usr/local/include/python3.13/pytypedefs.h:22:16: 附注：forward declaration of ‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
| ^~~~~~
vnpy_mini/api/include/pybind11/pybind11.h:1892:14: 错误：对不完全的类型‘PyFrameObject’ {aka ‘struct _frame’}的非法使用
1892 | frame->f_code->co_argcount > 0) {
| ^~
/usr/local/include/python3.13/pytypedefs.h:22:16: 附注：forward declaration of ‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
| ^~~~~~
vnpy_mini/api/include/pybind11/pybind11.h:1895:18: 错误：对不完全的类型‘PyFrameObject’ {aka ‘struct _frame’}的非法使用
1895 | frame->f_locals, PyTuple_GET_ITEM(frame->f_code->co_varnames, 0));
| ^~
/usr/local/include/python3.13/pytypedefs.h:22:16: 附注：forward declaration of ‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
| ^~~~~~
包含于文件 /usr/local/include/python3.13/Python.h:63:
vnpy_mini/api/include/pybind11/pybind11.h:1895:52: 错误：对不完全的类型‘PyFrameObject’ {aka ‘struct _frame’}的非法使用
1895 | frame->f_locals, PyTuple_GET_ITEM(frame->f_code->co_varnames, 0));
| ^~
/usr/local/include/python3.13/pyport.h:19:38: 附注：in definition of macro ‘_Py_CAST’
19 | #define _Py_CAST(type, expr) ((type)(expr))
| ^~~~
/usr/local/include/python3.13/cpython/tupleobject.h:27:38: 附注：在宏 ‘_PyTuple_CAST’ 展开时
27 | #define PyTuple_GET_ITEM(op, index) (_PyTuple_CAST(op)->ob_item[(index)])
| ^~~~~~~~~~~~~
vnpy_mini/api/include/pybind11/pybind11.h:1895:30: 附注：在宏 ‘PyTuple_GET_ITEM’ 展开时
1895 | frame->f_locals, PyTuple_GET_ITEM(frame->f_code->co_varnames, 0));
| ^~~~~~~~~~~~~~~~
/usr/local/include/python3.13/pytypedefs.h:22:16: 附注：forward declaration of ‘PyFrameObject’ {aka ‘struct _frame’}
22 | typedef struct _frame PyFrameObject;
| ^~~~~~
error: command '/usr/bin/g++' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for vnpy-mini
Failed to build vnpy-mini
