Log file Viewer

[00:17:17] <jaraco> you don’t even need to unpack a wheel. Just create a PathDistribution for a zipfile.Path over a Zipfile object opened on the wheel stream from pypi. Don’t even need to save it to the file system.

[00:18:05] <jaraco> let me make a demo

[00:29:03] <jaraco> https://gist.github.com/fa1bfe2feb7fb229e37b8b8e519c7a17

[07:36:36] <nanonyme> jaraco, too bad wheel spec doesn't fully replace sdists since C extensions convolute the situation. That looks neat

[13:58:28] <Xelnor> Hello folks! I've got a question: I know that `pip install wheel` is required if I want to generate wheels of my packages; but is it required if I want pip to download and install wheels? Or only if I want pip to locally build and cache wheels? It doesn't seem to be a direct dependency of pip

[14:01:49] <ngoldbaum> Xelnor: pip bundles its dependencies, you don’t need wheel installed for pip to handle wheels

[14:02:56] <ngoldbaum> c.f. https://github.com/pypa/pip/tree/master/src/pip/_vendor

[14:03:14] <ngoldbaum> although wheel isn’t in there so maybe pip doesn’t use the wheel library at all

[14:03:54] <Xelnor> ngoldbaum: thanks! from local experiments, it looks like pip has a built-in support for "Installing .whl files"; however, the support for "Building and caching wheels locally" requires the wheel package to be installed :)

[14:04:15] <ngoldbaum> yup

[14:04:50] <ngoldbaum> wheel is just a zip file so something installing them doesn’t need to know a ton about them

[14:05:58] <Xelnor> yep

[14:47:53] <tos9> Xelnor: The way you handle installing wheel to build your package is that your package should have a pyproject.toml, and that file should be saying wheel is required, and then wheel will be installed when you build your package

[14:48:08] <tos9> (whether that's with pip, some other builder, `build`, etc.)

[20:42:53] <graingert> I'm about to start debugging https://readthedocs.org/projects/twisted/builds/12508517/

[20:44:49] <graingert> hmm this might be a real pip bug

[20:45:21] <graingert> pradyunsg: `/home/docs/checkouts/readthedocs.org/user_builds/twisted/envs/1491/bin/python -m pip install --upgrade --upgrade-strategy eager --no-cache-dir .[dev]` . in this case is twisted

[20:45:42] <graingert> it's trying to collect: `Collecting Twisted[tls]>=18.7.0`

[20:50:29] <tos9> not sure that part looks like a bug

[20:50:36] <tos9> it's doing that because that's indeed what treq says its requirement is

[20:51:09] <tos9> maybe it should preoptimize this case knowing it's in the process of installing twisted itself so it should prefer that as the version until otherwise that won't work

[20:51:20] <tos9> but even if it didn't it shouldn't blow up later when backtracking

[20:51:30] <tos9> so the bug seems to me like it's somewhere later.

[21:05:46] <graingert> trying this: https://github.com/graingert/twisted/pull/new/pip-2020-resolver

[21:07:22] <graingert> hmm we're installing twisted[dev] not twisted[tls] here

[21:10:53] <graingert> oh no: ERROR: Requested toml from files.pythonhosted.org/packages/af/06/edd820aa8a04ba82354a841af00aa28dcde391a7759a1e34579bb33d63bf/toml-0.9.3.1.tar.gz#sha256=e1e8c220046889234df5ec688d6f97b734fc4a08a6d8edfc176f4e6abf90cfb5 (from towncrier>=17.4.0->Twisted==20.3.0.dev0) has different version in metadata: '0.9.3'

[21:21:18] <graingert> Why is it still trying multiple treq versions?

[21:21:36] <graingert> Oooh do I need a twisted @ file://.

[21:26:22] <graingert> nope I'm using tox here

[21:31:37] <graingert> and it's failing on tox and on rtd builder

[23:54:23] <jaraco> @nanonyme: For sdists, there’s another option. It does require extracting the sdist to a temporary directory (a limitation imposed by the PEP 517 spec), but with `pep517.meta`, it’s possible to extract metadata from an unbuilt package.

[23:56:44] <jaraco> (`pep517.meta.load` in particular)