<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>虚拟环境重建后 TLS 悄悄断了：certifi 死路径故障链的复现与修复 :: x7peeps</title><link>https://x7peeps.com/AI/06-AI%E5%B7%A5%E7%A8%8B%E5%8C%96/%E8%99%9A%E6%8B%9F%E7%8E%AF%E5%A2%83%E9%87%8D%E5%BB%BA%E5%90%8E-TLS-%E6%82%84%E6%82%84%E6%96%AD%E4%BA%86certifi-%E6%AD%BB%E8%B7%AF%E5%BE%84%E6%95%85%E9%9A%9C%E9%93%BE%E7%9A%84%E5%A4%8D%E7%8E%B0%E4%B8%8E%E4%BF%AE%E5%A4%8D/index.html</link><description>有个报错在 Python 圈并不罕见：进程跑着跑着，所有 HTTPS 请求突然全挂——httpx 系报 [Errno 2] No such file or directory（发生在客户端构造那一刻），requests 系报 OSError: Could not find a suitable TLS CA certificate bundle, invalid path: …/certifi/cacert.pem。第一反应通常是网络坏了、代理坏了、证书过期了。三样都不是：坏的是一个本地文件路径——你的 Python 环境目录被包管理器原地换掉了，而进程还记得旧路径。</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate/><atom:link href="https://x7peeps.com/AI/06-AI%E5%B7%A5%E7%A8%8B%E5%8C%96/%E8%99%9A%E6%8B%9F%E7%8E%AF%E5%A2%83%E9%87%8D%E5%BB%BA%E5%90%8E-TLS-%E6%82%84%E6%82%84%E6%96%AD%E4%BA%86certifi-%E6%AD%BB%E8%B7%AF%E5%BE%84%E6%95%85%E9%9A%9C%E9%93%BE%E7%9A%84%E5%A4%8D%E7%8E%B0%E4%B8%8E%E4%BF%AE%E5%A4%8D/index.xml" rel="self" type="application/rss+xml"/></channel></rss>