Log file Viewer

[02:53:57] <disi> should setup_requires be left in setup.py in projects that have a PEP 518 [build-system]?

[02:55:34] <toad_polo> It's unnecessary but doesn't hurt anything. It will likely be removed eventually.

[02:56:31] <disi> the main reason I could think of is to accommodate older installers

[02:56:52] <disi> do 517 builders just ignore it?

[02:56:53] <toad_polo> The main reason to leave it there is to support... Yes.

[02:57:30] <toad_polo> Well the only build backend that supports setup.py is setuptools.

[02:57:56] <toad_polo> It takes the setup_requires and has it installed at a slightly different time I think.

[02:58:08] <disi> interesting

[02:58:56] <disi> also interesting is (sensibly) being able to have 2 different setuptools minversions

[02:59:25] <toad_polo> First the build-system.requires gets installed, then the front end calls a function to get the requirements for building a wheel or sdist, then the pip installs those.

[02:59:47] <toad_polo> Hmmm... I would not recommend that, but good point. 😛

[03:40:36] <njs> toad_polo: are setup_requires integrated with the PEP 517 requirements fetching thing?

[03:40:49] <toad_polo> Apparently.

[03:41:11] <toad_polo> I didn't do it, I just found out about it because it's slightly broken.😛

[03:41:23] <njs> that's pretty awesome though

[03:41:49] <njs> silly me, I assumed the fact that it was left broken for so long was because there was some intrinsic reason why pip couldn't extract them :-)

[03:42:00] <ngoldbaum> lol, setup_requires will start actually working now?

[03:42:09] <toad_polo> Not really.

[03:42:33] <toad_polo> It's only useful for stuff like setuptools plugins.

[03:43:07] <toad_polo> Anything you need to import wouldn't be installed until after setup is called without some extra fiddliness.

[03:44:25] <toad_polo> I suppose there's a way to read them from setup.cfg before setup.py is executed, though.

[03:44:37] <njs> toad_polo: but that's already true today, except that today it also corrupts your environment in exciting ways by using easy_install

[03:44:59] <toad_polo> njs: Oh, yeah, that part's true.

[20:29:28] <icantodd> hey guys, will there be support for api tokens in warehouse so that apps like poetry and twine can use api keys?

[21:10:20] <toad_polo> icantodd: Looks like the ticket for that is here: https://github.com/pypa/warehouse/issues/994

[21:11:12] <icantodd> thank ya! ill subscribe

[21:11:21] <icantodd> what about remembering logins for the web interface?

[21:11:58] <toad_polo> It's all the same issue tracker, maybe search around and see if you can find something appropriate.

[21:12:08] <toad_polo> If not feel free to open a new issue.

[21:12:17] <icantodd> sure thing

[21:12:21] <icantodd> thanks again

[23:17:30] <AzMoo> Hey, I'm having an issue with pip and the cairocffi package, and I'm not sure if it's the expected behaviour. cairocffi specifies its version using the "file: cairocffi/VERSION" syntax in setup.cfg to reference an external file. After installing cairocffi, running pip freeze will output the version as: "cairocffi===file-.cairocffi-VERSION"

[23:17:54] <AzMoo> I'm expecting an actual semver version string there. Is that expected behaviour or an issue in pip?

[23:18:59] <ngoldbaum> sounds like a bug in the package

[23:19:24] <AzMoo> setuptools documentation says this is a valid way of describing the version

[23:19:35] <ngoldbaum> then i guess it's a bug in setuptools

[23:19:46] <ngoldbaum> somehow that is ending up in the package metadata

[23:19:53] <ngoldbaum> pip is just reading the metadata

[23:19:54] <AzMoo> https://setuptools.readthedocs.io/en/latest/setuptools.html#metadata

[23:24:39] <AzMoo> how does pip read the metadata? Is it using pkg_resources?

[23:27:16] <ngoldbaum> AzMoo: ah you need to update setuptools it looks like https://github.com/Kozea/cairocffi/issues/123

[23:28:46] <AzMoo> How did I miss that? I've been trawling through issues for hours.

[23:29:59] <ngoldbaum> because it

[23:30:04] <ngoldbaum> 's closed probably

[23:30:32] <AzMoo> Yep. Also I'd updated setuptools already but it seems you have to update setuptools before it's installed.

[23:30:38] <AzMoo> Thanks v much

[23:31:34] <ngoldbaum> ah i see

[23:31:36] <ngoldbaum> makes sense

[23:31:39] <ngoldbaum> they should upload a wheel

[23:31:54] <ngoldbaum> or update the setuptools dep in their setup.py

[23:51:32] <toad_polo> ngoldbaum: They would need to update in pyproject.toml I think.

[23:58:10] <ngoldbaum> ah yes, sorry