Log file Viewer

[02:12:12] <pradyunsg> toad_polo: could you re-state your concerns with `pip build` in https://github.com/pypa/packaging-problems/issues/219?

[04:08:34] <pradyunsg> sumanah: if you see this later, thanks for asking! I can't think of any additional demographics.

[14:31:45] <ronny> I UK it but NH FL cc mumuckxx

[15:12:58] <pdxjohnny> Hi All, I'm not sure if this is a bug and if it exists in the issue tracker I was unable to find it. I have a project, https://github.com/intel/dffml that uses the entrypoint system to register "plugins" those "plugins" are spererate python packages. THey list the main framework they plug-into under their install_requires in their setup.py. I have the main package installed in development mode (pip install

[15:13:00] <pdxjohnny> -e .)

[15:14:01] <pdxjohnny> but then when I install one of the plugins in development mode the release version of the main package is fetched and installed, and the main-package.egg-link is then ignored. Now that I've written this, I think this might be a setuptools problem, thoughts?

[15:14:49] <pdxjohnny> I think the behavior shoudl be to not install a relaese version if you have a development version checked out, do people agree? or dissagree?

[15:17:52] <pdxjohnny> i'm gonna take this over to setuptools, since I think I am indeed missdirected coming here.

[16:48:57] <toad_polo> setuptools doesn't usually decide what packages to install in any actively supported code paths.

[16:49:19] <toad_polo> pdxjohnny: ^

[16:50:02] <pdxjohnny> toad_polo: is that distutils or pip? or something else?

[16:50:12] <toad_polo> I think pip doesn't try to install anything if it already exists, regardless of its version, unless you use pip install -U

[16:50:49] <toad_polo> Heh, distutils is less supported than setuptools.

[16:51:25] <toad_polo> pip is or should be doing all package installations, if everything you have to build is doing things right.

[16:52:03] <pdxjohnny> the issue also happens when doing `setup.py install`

[16:52:19] <pdxjohnny> still pip?

[16:52:28] <toad_polo> Yeah, that is setuptools, only use pip.

[16:53:06] <pdxjohnny> okay, but either way the release version is being installed, when an egg-link is present for the same librar

[16:53:33] <pdxjohnny> so then this might be an issue with both pip and setuptools? or maybe this is intended behavior, but I feel like it shouldn't be

[16:54:17] <toad_polo> It might be caused by setuptools, but almost certainly in an unsupported path.

[16:55:34] <pdxjohnny> sweet, I'll go check around in that code, and see what's up perhaps there's a comment or something saying that this is intened, if not I'll raise the issue in the python bug tracker, and then in pip then. Does that seem like a good plan? Thanks for your help with this

[16:56:34] <toad_polo> I would create a MWE before looking at the code, which is very messy.

[16:57:18] <toad_polo> Try `pip list`, do you see the package installed twice?

[16:57:49] <toad_polo> Or maybe some package with an unknown name?

[16:58:50] <toad_polo> This doesn't happen in general with `pip install -e . && pip install <pkg>`

[17:02:47] <toad_polo> So the most likely things I think would be happening would be 1. the package you are installing is pinning a minimum version higher than the one you have installed editable 2. the editable package generates different metadata than the PyPI name so pip can't know that it's already installed or 3. some weird problem with old versions of pip and/or setuptools, which would be solved by upgrading both.

[17:09:51] <ioakim> hi i was wondering if someone could help me locate where in the source code is a package verified before being installed. thanks