Log file Viewer

[01:49:41] <lb5tr> hey

[01:49:47] <lb5tr> i have a question about warehouse source code

[01:50:17] <lb5tr> i'm wondering if information about squatters is exposed somewhere to package owners

[01:50:36] <lb5tr> or is it only available to the site owners

[01:50:55] <lb5tr> https://github.com/pypa/warehouse/blob/da3d5b5a340c9a11e6d1c56e7a2b563a1f3ac5c8/warehouse/admin/templates/admin/projects/detail.html

[01:50:58] <lb5tr> this view exactly

[03:49:09] <di_codes> lb5tr: Only administrators.

[13:28:35] <MGough> Hey, hopefully someone here can help me. I'm having issues with development versions when using pip install. For example both '1.1.1.dev1' and '1.1dev1' are valid PEP440 versions, but when I try to pip install a requirements file which contains 'mydep=1.1.1.dev1' it fetches 1.1.1 instead. Although if I specify '--pre' it gets the specified version. This seems to go against the docs? https://pip.pypa.io/en/stable/reference/pip_install/

[13:37:09] <ngoldbaum> > The pip install command also supports a --pre flag that enables installation of pre-releases and development releases.

[13:37:33] <ngoldbaum> it doesn't make much sense that it doesn't install the version you ask it to though, maybe file a bug?

[13:37:45] <ngoldbaum> >

[13:37:45] <ngoldbaum> --pre

[13:37:45] <ngoldbaum> Include pre-release and development versions. By default, pip only finds stable versions.

[13:38:48] <MGough> Yeah, it's rather odd. Based on my understanding of the docs if I specify a development version, as long as I don't use '!=' it should retrieve that version, it being a special case of pre-release

[13:39:15] <MGough> So I have this running in a pipeline and haven't seen any issues with it until very recently, so I'm wondering if perhaps it is a bug in 19.1

[13:41:38] <ngoldbaum> if it used to work and doesn't anymore that's stronger evidence that it's a bug

[13:41:44] <ngoldbaum> i'd file an issue on pip's github

[13:41:53] <ngoldbaum> search if someone else has reported it first

[13:42:43] <MGough> I'll just trawl through our jenkins logs to confirm my suspicion, I had a look at the issues on github but couldn't spot anything

[13:46:41] <MGough> Ah I was wrong, it appears to have been the same since prior to 19.1

[14:01:37] <MGough> I'll test it out with a different package, perhaps my own one is just doing something strange

[14:08:02] <MGough> Strange, it seems to work fine for a different package. Think I must be doing something silly! Will delve into it in verbose mode and leave you lot in peace. Thanks for the sanity check ngoldbaum

[15:19:32] <sumanah> heads-up folks https://mail.python.org/archives/list/pypi-announce@python.org/thread/YTZWD5H4H3VCQTQVPRDLH2TTHVTJS7JQ/ and https://twitter.com/ThePyPA/status/1123968122925527041 are up. 2-factor auth on PyPI is on the way

[19:20:29] <waynew> \o/ 2fa FTW