[09:56:51] <rindolf> Hi all! Would you guys appreciate a pypi equivalent to https://qa.perl.org/cpan-testers/ ?
[12:39:22] <ssbarnea> is here the right place to discuss pypi CDN issues? i got logs of flaky "No matching distribution found " errros on CI since the migration.
[12:41:52] <mgedmin> it's a good place to discuss those, I think
[12:46:07] <ssbarnea> mgedmin: we get more and more of these, on normal / random packages. my impression is that some CDN servers are reporting 404 for some folders and making pip believe packages do not exist. It doesn't retry, it just fails right away.
[12:47:59] <ssbarnea> mgedmin: here is one example: https://gist.github.com/ssbarnea/62d2374d9f101d5f596f27c136015d39
[12:48:30] <ssbarnea> and the problem is not specific to today, happened since the upgrade, seems random in nature.
[12:49:09] <mgedmin> how hard is it to reproduce this at will?
[12:51:44] <ssbarnea> mgedmin: i expect >100 occurences in last two weeks, maybe like 2-3% of builds. this is "impression" but I should be able to query the mongodb to give exact numbers.
[12:52:11] <ssbarnea> lucky for me I got a pattern check for this kind of error, so i only need to perform a query, which is not as easy as SQL.
[12:53:57] <ssbarnea> but if not really needed i would prefer to avoid the query task
[12:54:11] <mgedmin> if you had to get the output of pip install -v <something> failing like that, how hard would that be
[12:54:27] <mgedmin> note: I'm just a curious bystander, with no access to pypi infrastructure
[12:54:48] <mgedmin> I can't be sure what will be useful to actual sysadmins once they notice this conversation
[13:41:42] <ssbarnea> ok, in this case I will activate -v for a while. can I do it via PIP_ vars?
[13:47:24] <mgedmin> -v is --verbose, so PIP_VERBOSE=1 should work
[15:04:21] <di_codes> ssbarnea: we’ve had similar reports with jenkins, could you leave a comment on <https://github.com/pypa/warehouse/issues/3826> if you see this again?
[16:55:08] <carlwgeorge> The packaging tutorial says "If you are using setuptools, you don’t need to list README.rst in MANIFEST.in." Is that also true if you are using a README.md file?
[16:55:59] <nedbat> carlwgeorge: if in doubt, just list it
[16:56:58] <Wooble> carlwgeorge: you don't need it for README.{rst,txt,md} https://github.com/pypa/setuptools/blob/89ef5bb7e4812193d6f593d531bad36191517981/setuptools/command/sdist.py#L40
[18:12:20] <sumanah> I could use some help from folks here -- I'm working on making https://github.com/econ-ark/HARK pip-installable (and then I'll use conda-skeleton to make it conda-installable). My work-in-progress branch is https://github.com/brainwane/HARK/tree/installability
[18:12:23] <sumanah> As of this moment, on my installability branch, in a Python 2.7.13 virtualenv using the system setuptools (version 39.1.0), if I run python setup.py sdist, it dutifully creates dist/HARK-0.8.0.tar.gz which is about 25M in size (a lot of that is cAndCwithStickyE/Results). pip will dutifully install HARK and its dependencies but then you can't actually import any of it yet, what with the __init__s not working and so on.
[18:12:38] <sumanah> TODO: I need to get install_requires working nicely with requirements.txt, I need to specify version numbers and (I believe) add some further package requirements that the developers so far haven't had to worry about because Anaconda always bundles them, and there's a bunch of other polish I need to do.
[18:13:18] <sumanah> so my main question right now is: how do I avoid duplication between requirements.txt and the install_requires argument in setup.py? https://packaging.python.org/discussions/install-requires-vs-requirements/ is confusing me a little
[18:13:53] <sumanah> (I'm trying to do 1 thing at a time here, so, porting to Python 3 is on our roadmap but *not just yet*)
[18:16:56] <ngoldbaum> requirements is for a specific deployment of your app
[18:17:08] <ngoldbaum> it sets the *exact* dependency versions you want to use for that deployment
[18:17:11] <sumanah> (side note: Ben Folds is my soundtrack here, in case anyone wants to really understand my situation in full stereo)
[18:17:29] <ngoldbaum> install_requires specifies the minimal dependencies needed
[18:17:47] <ngoldbaum> if you need to specify version constraits (i.e. for a minimum version number or to pin something)
[18:17:51] <ngoldbaum> you can do that in install_requires
[18:17:55] <ngoldbaum> but only if you really need ot
[18:18:32] <ngoldbaum> IMO projects shouldn't ship a requirements file unless they're building a webapp or something like that that needs *very* specific versions of dependencies
[18:18:57] <sumanah> So I think I don't need requirements.txt .... is it like, often, requirements.txt is for libraries that need to be super specific about dependencies, and install_requires is more appropriate for applications that do not need to be THAAAAT specific?
[18:19:06] <sumanah> thank you for your help ngoldbaum