Log file Viewer

[04:11:38] <pradyunsg> FFY00: that's what pip does today in terms of rejecting compatibility.

[07:06:08] <McSinyx[m]> FFY00, I think I didn't made myself clear, I meant something similar to cibuildwheel but it's a pep517 backend (instead of using setuptools to build and auditwheel/delocate to fix the wheel after)

[07:09:08] <McSinyx[m]> making users building from source would impact the performance a bit, but telling them to install C/C++ dependencies is not an easy task and a lot of things can go wrong with a slight difference in version

[07:09:43] <McSinyx[m]> that being said, it's unlikely that any of us here is going to volunteer on writing such backend any time soon

[07:11:42] <McSinyx[m]> AFAIK there's not even a way to automate wheel ``repairing'' on Windows---what e.g. numpy does is pure black magic

[10:32:29] <FFY00> why would you ever relink dependencies?

[10:33:02] <FFY00> the the soname is different, the ABI probably changed

[10:34:17] <FFY00> relinking might seem to work, but you might get random crashes and weird behaviors

[10:34:44] <FFY00> anyway, I probably should look into this before keep criticizing it :P

[10:35:00] <FFY00> this is just my POV from the outside

[13:16:53] <McSinyx[m]> as an user, all I can tell is that it is not convenient at all to compile some specific version of dependencies just to get one piece of software working

[13:17:49] <McSinyx[m]> it's basically the `pip install xxx` vs `git clone this && make this && git clone that && make that && ... && pip install`

[13:19:56] <McSinyx[m]> I know that it is borderline chaotic (and hopefully chaotic good) to put 5-7 .so in a zip file and relink other .so to it, but it saves the users from having to manage dependenies by hand

[13:21:47] <McSinyx[m]> the best solution would be to have them in a coordinated repository which takes care of dependencies management (so that every package only exists at exactly one version at a time) like that of most unix-like OSes, but that seems to belong to another scope

[13:22:41] <McSinyx[m]> IMHO pip and PyPI exists for platforms without such repos and for packages that are not popular enough to be included

[14:29:18] <tos9> what version of warehouse does warehouse run

[14:29:50] <tos9> or I guess more specifically

[14:30:08] <tos9> di_codes: do you know if https://github.com/pypa/warehouse/pull/8191/files is already running on pypi.org?

[14:49:11] <tos9> ok I think finding https://github.com/pypa/warehouse/issues/918 tells me that warehouse autodeploys on master so that answers that I think

[22:40:09] <FFY00> McSinyx[m], I dream of someday being able to create virtual envs by linking against system packages

[22:40:52] <FFY00> in which case, you would install these problematic packages via the distro package manager, which is ready to handle such cases

[22:41:11] <FFY00> that's actually in my TODO, but ETIME

[22:43:05] <FFY00> anyway, I think it's much more convenient to have pip compiling some dependencies than to have the software randomly crash or have obscure errors

[23:54:09] <travis-ci> pypa/pip#17670 (master - 5ef3dd1 : Paul Moore): The build is still failing.

[23:54:09] <travis-ci> Change view : https://github.com/pypa/pip/compare/46b938349abc8b57a8f132b9859c24b9620cb380...5ef3dd1a54df6cee0377dfd3e34e9ebbcfae37ed

[23:54:09] <travis-ci> Build details : https://travis-ci.org/pypa/pip/builds/718457446