Log file Viewer

[17:42:17] <bmbouter> perhaps the warehouse changes broke pip in my env?

[17:42:39] <bmbouter> when I `pip install pulp-core-plugin` it says Failed to establish a new connection: [Errno -2] Name or service not known',)': /simple/pulp-core-plugin/

[17:43:15] <bmbouter> oh wait there is another problem

[17:43:17] <bmbouter> please disregard

[17:52:23] <bmbouter> actually I can't `pip install pulpcore` that was working before

[17:56:48] <hbf> bmbouter: Maybe you need to tweak your firewall rules. When we upgraded to RHEL 7.5, pip moved to a fetching from a different domain.

[18:10:54] <bmbouter> hbf: ty

[18:11:02] <bmbouter> I was able to get it resolved due toa dns issue

[20:33:20] <jellycode> hey guys, sorry for this novice question. i was using twine to upload to private pip repo before. I didn't understand things clearly at first, so I filled in pip.conf, plus some env vars, plus ~.pypirc with the URL and auth info.

[20:33:37] <jellycode> I also setup jenkins to auto build and push packages there

[20:34:20] <jellycode> Later, i was able to just do python setup.py sdist upload, and upload was working, seemingly without dealing with twine

[20:35:08] <jellycode> Now that same command is prompting me for password. I'd like to keep things as simple as possible, so would like to see if i can make work without involving twine

[20:35:39] <ngoldbaum> you really want to use twine

[20:35:49] <ngoldbaum> setup.py sdist upload is all but deprecated

[20:35:59] <jellycode> Ok then, that settles it

[20:36:04] <ngoldbaum> it also prevents you from testing the sdist before uploading, which is considered bad practice

[20:36:24] <jellycode> So, do i still need to maintain parallel configs for pip.conf and .pypirc ?

[20:37:07] <ngoldbaum> i don't know offhand, maybe?

[20:38:14] <jellycode> well, if i delete pip.conf, i don't expect pip install mypackage to be able to search my private repo right?

[20:39:05] <jellycode> TBH, pip install mypackage hasn't even been working on my build servers

[20:39:20] <jellycode> I have to manually append --extra-index-url=myserver to get it to install the damn package

[20:39:29] <jellycode> still gotta fix that

[20:52:45] <dstufft> jellycode: FWIW the two files do different things

[20:53:11] <dstufft> jellycode: ~/.pypirc defines where your uploader (in this case, twine) can upload files too, and credentials to do that with

[20:53:32] <dstufft> jellycode: pip.conf tells pip where to _download_ files from (and some other configuration as well)

[20:53:45] <dstufft> sometiems these point to the same place, with the same credentials, sometimes they don't

[20:53:48] <jellycode> yeah, i do understand that, but obviously the situation is undesirable, and pretty unique to PIP as a package manager, and only because of the split between the package and upload tool and the download tool.

[20:54:00] <jellycode> was hoping there was a plan to "reconverge"

[20:54:12] <dstufft> jellycode: eh, historically most package managers had seperate upload tools :)

[20:54:37] <dstufft> some of the newer language ones have combined tools

[20:55:12] <dstufft> there's no right answer to that though, sometiems you want the same verbs to mean slightly different things if you're installing vs uploading/managing a project

[20:55:14] <jellycode> pip had them together, and then it split because the tools split. this was a regression from a user-experience usability perspective.

[20:55:24] <dstufft> pip never supported uploading files

[20:55:49] <jellycode> python setup.py sdist upload required no additional python packages

[20:56:19] <jellycode> i will stop making the point however, it's of no value

[20:56:38] <dstufft> that's not pip, that's using either distutils or setuptools (or something else all together) depending on what you imported in the setup.py

[20:57:05] <jellycode> it used info from pip.conf

[20:59:05] <dstufft> I cannot recall it ever doing that, and I would be very surprised to find that to be the case knowing those projects as well as I do