Log file Viewer

[03:45:54] <kober> Hi, I'm generated some static wheels like this: pip wheel -w wheelhouse -r requirements.txt, then I try to use that directory: pip install --no-index --find-links ./wheelhouse dist/*.whl  and I get the error ERROR: Could not find a version that satisfies the requirement uvloop<0.15.0,>=0.14.0 or ERROR: Could not find a version that satisfies the

[03:45:54] <kober> requirement PyYAML==5.4.1

[03:46:18] <kober> I have these files in that directory: PyYAML-5.4.1-cp39-cp39-manylinux1_x86_64.whl and uvloop-0.14.0-cp39-cp39-manylinux1_x86_64.whl

[03:47:04] <kober> Do you know why those files wouldn't satisfy the requirement?

[03:48:45] <kober> Interesting, trying to install the wheel manually it says "ERROR: PyYAML-5.4.1-cp39-cp39-manylinux1_x86_64.whl is not a supported wheel on this platform."  but I built the wheel on that platform.  Its just a docker alpine container

[03:50:01] <kober> I generated it by doing "auditwheel repair <file>" where <file> was the result from pip wheel -w wheelhouse -r requirements.txt

[03:53:13] <kober> >>> platform.architecture():  ('64bit', ''). and python3 --version: Python 3.9.1

[03:53:17] <kober> It should be compatible?

[03:53:38] <kober> pip --version

[03:53:39] <kober> pip 21.0 from /usr/local/lib/python3.9/site-packages/pip (python 3.9)

[04:08:54] <kober> If I grab `from packaging.tags import sys_tags` I get the following:  [str(x) for x in supported_tags]

[04:08:55] <kober> ['cp39-cp39-linux_x86_64', 'cp39-abi3-linux_x86_64', 'cp39-none-linux_x86_64', 'cp38-abi3-linux_x86_64', 'cp37-abi3-linux_x86_64', 'cp36-abi3-linux_x86_64', 'cp35-abi3-linux_x86_64', 'cp34-abi3-linux_x86_64', 'cp33-abi3-linux_x86_64', 'cp32-abi3-linux_x86_64', 'py39-none-linux_x86_64', 'py3-none-linux_x86_64', 'py38-none-linux_x86_64',

[04:08:55] <kober> 'py37-none-linux_x86_64', 'py36-none-linux_x86_64', 'py35-none-linux_x86_64', 'py34-none-linux_x86_64', 'py33-none-linux_x86_64', 'py32-none-linux_x86_64', 'py31-none-linux_x86_64', 'py30-none-linux_x86_64', 'py39-none-any', 'py3-none-any', 'py38-none-any', 'py37-none-any', 'py36-none-any', 'py35-none-any', 'py34-none-any', 'py33-none-any',

[04:08:56] <kober> 'py32-none-any', 'py31-none-any', 'py30-none-any']

[04:09:35] <kober> So does `-cp39-cp39-manylinux1_x86_64` not match `cp39-cp39-linux_x86_64`?

[05:58:04] <hotel> hiya, i'm testing automatic deployment to pypi from azure pipelines and i appear to be running into this issue https://github.com/pypa/warehouse/issues/8565 ... token was generated only an hour or two ago at most, and I'm using a .pypirc file adapted from the one the token generation page offers. anyone have ideas on how to fix this? should i just

[05:58:04] <hotel> open a new issue at warehouse? tia

[05:59:07] <hotel> i assume questions about using twine are on topic here, if not i apologise ><

[18:30:45] <hotel> !logs

[18:30:45] <pmxbot> http://kafka.dcpython.org/channel/pypa

[18:36:39] <ngoldbaum> hotel: i’d just comment on that issue or create a new one, this is a low traffic channel and isn’t great for direct support, esp on weekends

[18:43:39] <hotel> fair play

[18:44:16] <hotel> taking a second look at my pypirc and i think i misunderstood what the fields do so i'm gonna try fixing that first