Date: Mon, 29 Dec 2014 17:20:58 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: maintainer-feedback requested: [Bug 196357] lang/python27 ssl certificate error, python interpreter not finding SSL pem file Message-ID: <bug-196357-21822-IWFezCtNjj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-196357-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-196357-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Tony <tony@git-pull.com> has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to python@FreeBSD.org: Bug 196357: lang/python27 ssl certificate error, python interpreter not finding SSL pem file https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196357 --- Description --- Created attachment 151077 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=151077&action=edit Info on installed python package So far I haven't been able to find ticket shows this behavior. I'm also trying to determine whether or not this is a bug, because I think that ports are supposed to install their dependencies to /usr/local (expected behavior?) http://unix.stackexchange.com/questions/176294/what-should-i-do-about-python-2- 7-9-not-looking-for-ssl-certificates-in-the-righ I got this when using `python setup.py register`. > $ python setup.py register > running register > running egg_info > writing requirements to tmuxp.egg-info/requires.txt > writing tmuxp.egg-info/PKG-INFO > writing top-level names to tmuxp.egg-info/top_level.txt > writing dependency_links to tmuxp.egg-info/dependency_links.txt > writing entry points to tmuxp.egg-info/entry_points.txt > reading manifest file 'tmuxp.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: no files found matching 'package_metadata.py' > writing manifest file 'tmuxp.egg-info/SOURCES.txt' > running check > warning: check: Could not finish the parsing. > Registering tmuxp to https://pypi.python.org/pypi > Server response (500): <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] > certificate verify failed (_ssl.c:581)> I can fix it by using > sudo ln -s /usr/local/etc/ssl/cert.pem /etc/ssl/cert.pem As mentioned in the stackexchange post. Another commenter there also said they didn't find an issue for this. I'd guess some (possibly many) people are experiencing this. > $ which python > /usr/local/bin/python > tony at x230 in /tmp > $ /usr/local/bin/python --version > Python 2.7.9 --- Comment #1 from Bugzilla Automation <bugzilla@FreeBSD.org> --- Auto-assigned to maintainer python@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196357-21822-IWFezCtNjj>