I try install press but have err

hello everyone

I try install press but have err

remote: Total 3504 (delta 878), reused 1832 (delta 444), pack-reused 0 (from 0)
Receiving objects: 100% (3504/3504), 18.68 MiB | 29.52 MiB/s, done.
Resolving deltas: 100% (878/878), done.
Ignoring dependencies of press. To install dependencies use --resolve-deps
Installing press
$ /home/frappe/frappe-bench/env/bin/python -m pip install --quiet --upgrade -e /home/frappe/frappe-bench/apps/press
DEPRECATION: Building ‘ansible’ using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of ‘ansible’. Discussion can be found at Deprecate legacy `setup.py bdist_wheel` mechanism for building projects · Issue #6334 · pypa/pip · GitHub
DEPRECATION: Building ‘PyGithub’ using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of ‘PyGithub’. Discussion can be found at Deprecate legacy `setup.py bdist_wheel` mechanism for building projects · Issue #6334 · pypa/pip · GitHub
DEPRECATION: Building ‘tornado’ using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of ‘tornado’. Discussion can be found at Deprecate legacy `setup.py bdist_wheel` mechanism for building projects · Issue #6334 · pypa/pip · GitHub
DEPRECATION: Building ‘ansible-base’ using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of ‘ansible-base’. Discussion can be found at Deprecate legacy `setup.py bdist_wheel` mechanism for building projects · Issue #6334 · pypa/pip · GitHub
DEPRECATION: Building ‘circuitbreaker’ using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of ‘circuitbreaker’. Discussion can be found at Deprecate legacy `setup.py bdist_wheel` mechanism for building projects · Issue #6334 · pypa/pip · GitHub

DEPRECATION: Legacy editable install of press==0.7.0 from file:///home/frappe/frappe-bench/apps/press (setup.py develop) is deprecated. pip 25.3 will enforce this behaviour change. A possible replacement is to add a pyproject.toml or enable --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using --config-settings editable_mode=compat. Please consult the setuptools documentation for more information. Discussion can be found at Deprecate legacy `setup.py develop` mechanism for `pip install --editable` · Issue #11457 · pypa/pip · GitHub
ERROR: pip’s dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
frappe 15.86.0 requires boto3~=1.34.143, but you have boto3 1.39.14 which is incompatible.
frappe 15.86.0 requires cryptography~=44.0.1, but you have cryptography 41.0.7 which is incompatible.
frappe 15.86.0 requires posthog~=3.21.0, but you have posthog 3.0.1 which is incompatible.
frappe 15.86.0 requires pyOpenSSL~=25.0.0, but you have pyopenssl 23.2.0 which is incompatible.
frappe 15.86.0 requires pytz==2023.3, but you have pytz 2025.2 which is incompatible.
frappe 15.86.0 requires requests~=2.32.0, but you have requests 2.31.0 which is incompatible.
frappe 15.86.0 requires sql_metadata~=2.11.0, but you have sql-metadata 2.10.0 which is incompatible.
frappe 15.86.0 requires sqlparse~=0.5.0, but you have sqlparse 0.4.4 which is incompatible.

your dependencies version is not matching with the required dependencies for the frappe 15.86.0

you have to manage the dependencies based on the requirement