Log file Viewer

[07:03:19] <xsetech> !logs

[07:03:19] <pmxbot> http://kafka.dcpython.org/channel/pypa

[07:08:44] <xsetech> I'm following the instructions at https://setuptools.readthedocs.io/en/latest/setuptools.html, and I've just gotten to `twine upload --repository-url https://test.pypi.org/simple/ dist/*`. The command was changed from `twine upload --repository-url https://test.pypi.org/legacy/ dist/*` in commit 0fc2a2acd6cc64b37b67e5f42e4d15d8e734c01f

[07:08:51] <xsetech> Except when I run it I get: `InvalidPyPIUploadURL: It appears you're trying to upload to pypi.org but have an invalid URL. You probably want one of these two URLs: https://upload.pypi.org/legacy/ or https://test.pypi.org/legacy/.`

[07:09:50] <xsetech> I'm guessing this is a rare case of the documentation being more up to date than anything else :)

[07:10:56] <xsetech> Also, the webmaster of http://kafka.dcpython.org/channel/pypa should use a cert..

[07:12:47] <xsetech> (and ftr /legacy works for uploading)

[07:18:34] <xsetech> Note the documentation's url for installing (https://test.pypi.org/simple/) does work.

[17:15:02] <di_codes> xsetech: Thanks for pointing that out, you're right. I made <https://github.com/pypa/setuptools/pull/1957> to fix it.

[18:36:41] <mirko> a pypi hosted package is confusing me

[18:37:21] <mirko> named "pc-ble-driver-py" - which it says is available in version 0.14.1 - but it apparently isn't

[18:37:54] <ngoldbaum> what do you mean exactly?

[18:38:04] <mirko> https://pypi.org/project/pc-ble-driver-py/ and `pip3 search pc-ble-driver-py | grep -E "^pc-ble-driver-py"` say 0.41.1

[18:38:20] <ngoldbaum> https://pypi.org/project/pc-ble-driver-py/#files looks like it's available for py36-38 on a variety of platforms

[18:38:27] <mirko> pip3 install pc-ble-driver-py==0.14.1

[18:38:27] <mirko> Collecting pc-ble-driver-py==0.14.1 Could not find a version that satisfies the requirement pc-ble-driver-py==0.14.1 (from versions: 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.6.1, 0.6.2, 0.8.0, 0.8.1, 0.9.0, 0.9.1, 0.10.0, 0.11.0, 0.11.1, 0.11.2, 0.11.3, 0.11.4)

[18:38:31] <mirko> No matching distribution found for pc-ble-driver-py==0.14.1

[18:38:38] <ngoldbaum> are you on python3.5 by chance?

[18:39:02] <mirko> i was thinking the same, but no

[18:39:02] <mirko> python3 --version

[18:39:03] <mirko> Python 3.7.3

[18:39:18] <mirko> pypi lists 0.14.1 packages for 3.7

[18:39:26] <ngoldbaum> what OS?

[18:39:31] <mirko> debian stable (buster)

[18:39:37] <ngoldbaum> maybe your OS isn't new enough for manylinux2010?

[18:40:01] <mirko> is this a question i'm supposed to answer?

[18:40:09] <mirko> i don't even know what manylinux2010 is

[18:41:15] <ngoldbaum> https://www.python.org/dev/peps/pep-0571/

[18:41:41] <mirko> to me as a user pip tells me "hey, 0.14.1 is available" while when i try to install it it says "sorry, 0.11.4 is latest"

[18:41:56] <ngoldbaum> are you on the newest pip version?

[18:42:30] <mirko> pip3 --version

[18:42:31] <mirko> pip 18.1 from /usr/lib/python3/dist-packages/pip (python 3.7)

[18:43:06] <ngoldbaum> 0.11.4 was the last version published as a tarball

[18:43:15] <ngoldbaum> since then they've only published wheels for a few platforms

[18:43:24] <ngoldbaum> i'm not sure offhand why the wheels aren't installing for your system

[18:44:08] <ngoldbaum> oh it's this https://github.com/NordicSemiconductor/pc-ble-driver-py/issues/148

[18:44:15] <ngoldbaum> you need pip 19 or newer apparently

[18:45:13] <mirko> thanks

[18:46:45] <mirko> i hope that's not received as unconstructive rant, but as somebody who really appreciates python and its eco system, this is kinda surprising to me.. couldn't pip be a bit moe verbose about why it can't pick the selected version? or at least show me the version which i can install despite being inconsistent on search and install?

[18:47:19] <ngoldbaum> probably, you might open an issue on pip's issue tracker asking for a better error message in this case

[18:47:45] <mirko> will do, thanks for help and clarification!

[20:23:36] <exarkun> I am trying to fix https://github.com/PrivateStorageio/ZKAPAuthorizer/blob/master/setup.cfg to correctly declare that it has a runtime dependency on https://github.com/leastauthority/privacypass but this causes `pip install` of the former to fail while trying to install milksnake, a setup_requires dependency of the latter

[20:24:00] <exarkun> If the latter actually had to be built then I could understand this. However, it does not. It is already present in the environment into which the install is being performed.

[20:24:50] <exarkun> Expected behavior?

[20:25:55] <exarkun> https://pip.pypa.io/en/stable/reference/pip_install/#controlling-setup-requires doesn't make me hopeful of a good resolution here...

[20:26:00] <ngoldbaum> setup_requires is, as i understand it, a legacy setuptools thing that does not interact will with pip

[20:26:21] <ngoldbaum> so the path of least resistance might be to get privacypass to drop the use of setup_requires...

[20:27:54] <ngoldbaum> ah but that's how you're supposed to use milksnake

[20:28:00] <ngoldbaum> fun!

[20:28:14] <ngoldbaum> maybe toad_polo knows

[20:33:59] <exarkun> hm

[20:34:15] <exarkun> I just noticed that privacypass also install_requires milksnake, and the milksnake docs also suggest this

[20:34:25] <exarkun> though I'm not sure why

[20:35:07] <toad_polo> exarkun: milksnake is a runtime and a test-time dependency, like cffi.

[20:35:28] <exarkun> Looking at the generated code, I don't see any milksnake references

[20:35:40] <exarkun> but maybe milksnake doesn't provide a module named `milksnake` ...

[20:36:19] <exarkun> but yea okay

[20:36:33] <toad_polo> Oh maybe that's because `milksnake` is pulling in `cffi` indirectly.

[20:36:48] <toad_polo> I don't think I ever looked at the generated code.

[20:38:39] <toad_polo> In general you should drop `setup_requires` in favor of the `build-system.requires` key in `pyproject.toml`, but setuptools will actually append the contents of `setup_requires` to the requirements for building a wheel (and maybe an sdist) if they exist, rather than trying to install them itself.

[20:39:08] <exarkun> maybe milksnake docs should be updated to say that

[20:39:38] <toad_polo> Maybe.

[20:40:16] <toad_polo> Anyway, there's lots of things that could be going wrong here, I'm not clear which one is.

[20:41:53] <toad_polo> I'm not sure why `milksnake` isn't installing, but taking as a given that you can't install `milksnake` at all but it's already present with the right version in the location you're installing `privacypass` into, then it's possible that `privacypass` is already using `pyproject.toml` and it's trying to install a new copy of `milksnake` into the isolated build environment.

[20:42:29] <exarkun> It wasn't present because I convinced myself it was a build dependency only

[20:42:50] <toad_polo> I think the easiest way to fix it would be to make it so you can install `milksnake` if that's possible.

[20:43:24] <exarkun> Yea, well, NixOS, so not that. pip isn't allowed to download anything, just operate on what is handed to it locally.

[20:43:25] <toad_polo> I see.

[20:43:37] <exarkun> It's working now, though, after marking milksnake as a runtime dependency.

[20:43:51] <toad_polo> Sure, but you can just put a wheel in there, right?

[20:44:05] <toad_polo> But yeah, whatever, if you have it working no need to worry about it. :)

[20:44:19] <exarkun> fwiw - https://github.com/LeastAuthority/privacypass/pull/15/files

[20:47:02] <exarkun> and cannot land because windows CI is broken because choco rustup package sha256 changed

[20:47:58] <toad_polo> exarkun: Isn't it both a runtime and a build-time dependency?

[20:48:22] <exarkun> yes but that's what `propagatedBuildInputs` really means afaict

[20:49:10] <toad_polo> Ah