| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Upstream's setup.cfg has several oddities to it, including claiming an
RDEPEND on dev-python/build from when they copied their requirements.txt
verbatim into setup.cfg.
As for certifi specifically, it is handled in a fiddly try/except that
falls back to using a bundled copy that is copied over from certifi into
displaycal iff building a py2app/py2exe edition, and if that still
doesn't work, silently does nothing.
The object of all this is that if a custom cacert.pem is found
somewhere, it goes and sets os.environ['SSL_CERT_FILE'] to affect later
uses of urllib.request.
Reasonably enough, none of this is needed except on Windows and macOS,
so displaycal does precisely that: runs this entire thing only on
Windows and macOS. On Linux, it never even attempts to import certifi,
nor set an environment variable. So we shouldn't depend on it either.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Michał Górny <mgorny@gentoo.org>
|
Eli Schwartz
Nick Sarnie
GitWeb