حادثة شهادات Python: تحديث المفسّر وحده لا يكفي

Read this news or bug-fix article as reference material:
https://nethanelfitoussi.com/article/python-october-2026-certificate-update?lang=en

Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.

Use the article and its examples as references. Identify any missing project files before making changes.

If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.

Additional project setup instructions:
Review my Python project using https://blog.python.org/2026/10/python-3151-3149-31317/ and https://discuss.python.org/t/information-for-python-users-regarding-emudhra-emsign-ca-certificate-security-incident/109576 . Inventory all virtual environments, CI images, pip, certifi, optional uv and system CA bundles. The October 21 Python releases are 3.15.1, 3.14.9 and 3.13.17; incident guidance lists pip 26.2.2, certifi 2026.10.19 and uv 0.13.4 as minimums for those tools. Verify current vendor instructions. Use the official checksum-pinned pip bootstrap procedure; do not invent a wheel URL or checksum. Do not disable TLS, use --trusted-host, or assume replacing the interpreter updates old virtual environments. Propose local compatible updates and tests, preserve lockfiles, and stop before production changes.

Check the dated advisory and current official vendor guidance. Identify whether my installed version and configuration are affected before proposing a fix.

Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.