Log file Viewer

[10:13:09] <gaborbernat> related to https://github.com/pypa/pip/pull/6370

[10:13:19] <gaborbernat> So I get now pip is PEP compliant, but this now breaks peoples workflow without any sane workaround, I consider it as a PEP oversight. PEP-517/8 on purpose did not want to cover editable installs, considering something to be addressed down the line. As such I would argue PEP-517/PEP-518 no longer applies when editable install mode is enabled. It's the build frontend dependent on how this case is handled.

[10:13:32] <gaborbernat> In such a case, pip should fallback to the old system, until we define editable installs inside a PEP.

[11:50:43] <Aliezan> Hello guys, I am sorry to come here only to get help, I am a bit desperate xD

[11:51:41] <Aliezan> Is there any charitable soul who is willing to help on a should-be-small matter ?

[11:58:20] <nedbat> Aliezan: on IRC it works better to ask your question directly. People don't often volunteer as experts, and sometimes non-experts can help.

[12:02:17] <Aliezan> Okay, thank ou nedbat. Here's the little issue I am facing: I have a python package (python3-mpi4py-mpich) installed through my distro's (Fedora) package manager (dnf), and am installing a python library I downloaded locally with 'pip install -e .'. my mpi4py install isn't detected and pip tries to install it from pipy

[12:03:51] <Aliezan> I feel like it's because the mpi4py package is in a subdirectory: "/usr/lib64/python3.7/site-packages/mpich/mpi4py" (I also have "/usr/lib64/python3.7/site-packages/openmpi/mpi4py")

[12:04:59] <nedbat> Aliezan: you should try asking in #python

[12:05:20] <Aliezan> Okay! thanks :)

[20:22:23] <lasko> I'll preface this with I'm a total newb to setuptools. Is it possible to publish a single egg distribution with multiple built tags? e.g. my-package-v0.0.1 and also my-package-master which would point to the same thing

[22:44:01] <tos9> lasko: (not egg, eggs are dead for >5 years)

[22:44:31] <tos9> lasko: you can push the same underlying set of files as multiple versions, but PyPI only accepts files following a certain convention

[22:44:55] <tos9> Which is different from you say, building such 2 copies of a file yourself and not then uploading them to PyPI -- you're welcome to do that part

[22:45:07] <tos9> But PyPI will not let you upload a file called my-package-master, it has to have a version

[22:45:14] <tos9> (And in fact one compatible with something called PEP 440)

[22:45:28] <tos9> Which roughly says "it has to look like a normalish version, either semver-y or date based"

[22:46:41] <tos9> So, tl;dr on probably what you're *actually* trying to do -- if you want the ability to install HEAD out of your VCS, pip can do that just fine, but don't upload that to PyPI

[22:47:04] <tos9> Just use `pip install git+https://your/git/repo@master`, or tell your users to do that if they want HEAD.

[22:51:58] <lasko> Thanks tos9.

[22:52:13] <tos9> np