Log file Viewer

[04:11:48] <wiggy> how long is "pipenv lock" supposed to take?

[04:15:05] <wiggy> average here seems to be over a minute :(

[04:47:11] <wiggy> after trying for an hour pipenv lock finally completed without a timeout

[04:47:15] <wiggy> took 4 minutes

[06:16:05] <wiggy> oh oh

[07:22:02] <techalchemy> wiggy: locking takes as long as it takes, currently

[07:22:25] <wiggy> techalchemy: it took me over an hour to lock this morning

[07:22:36] <wiggy> it kept timing out so I would have to restart

[07:22:39] <techalchemy> you said the average was a minute

[07:22:58] <techalchemy> if it's taking you an hour there's obviously a problem

[07:23:00] <wiggy> no, I said "over a minute", the example I pasted was 1m54s

[07:23:18] <techalchemy> if it's taking you a minute that is not an hour, even if it's two minutes it's not an hour

[07:23:24] <wiggy> this morning network here was a bit slower and I got a pypi timeout after 4+ minutes all the time

[07:23:50] <techalchemy> what are you trying to lock?

[07:23:51] <wiggy> so run the command, do something else, look at terminal and notice timeout exception, try again, rinse repeat

[07:24:11] <wiggy> A pipfile that just has "-e ."

[07:24:16] <wiggy> and I needed to update a single dependency

[07:24:30] <techalchemy> okay that isn't helpful

[07:24:33] <techalchemy> what is in your setup.py

[07:24:47] <techalchemy> anything? 2 packages? 200 packages?

[07:24:47] <wiggy> the pypi timeouts this morning made it worst case, and I didn't think it was fair to blame all of that on pipenv

[07:24:54] <techalchemy> it's still an issue

[07:25:08] <wiggy> 21 dependencies

[07:25:20] <wiggy> with all indirect dependencies the whole thing is 72 packages iirc

[07:25:40] <wiggy> I can't include pipenv.help output until the security issues there are fixed

[07:26:08] <techalchemy> idk what the security issues are that you're referring to

[07:26:18] <wiggy> the very next issue I filed :)

[07:26:23] <techalchemy> but i'm sure you can scrub your own data

[07:26:38] <wiggy> issue 1915

[12:12:09] <eric97477> I had a quick question about pip download. It has several flags that I would like to play with --platform, --abi, --implementation. Where can I find documentation on valid values for these flags?

[12:12:09] <eric97477> The documentation at https://pip.pypa.io/en/stable/reference/pip_download/ mentions some examples, but not a complete list.

[12:17:42] <mgedmin> eric97477: iirc there was a pep, possibly this one: https://www.python.org/dev/peps/pep-0425/#details

[12:18:42] <mgedmin> plus extensions like manylinux: https://www.python.org/dev/peps/pep-0513/

[12:23:59] <eric97477> Thank you. I am curious...pip download can, I believe, determine these values for the current system on which it is running...correct? Is there a way to ask for the the value of --platform, --abi, --implementation for the current system?

[13:29:54] <akemot> how does package download counter work at pypi, is it incremented for a single ip?

[13:40:31] <akemot> say, there're cryptography, crytography, cryptogaphy packages in pypi. I want to assume, the more downloads package has, the more credible it is

[13:42:55] <dstufft> akemot: everytime someone downloads a file it gets incremented, we don't do any filtering or rollups to try to deduplicate since anything we could do is just going to introduce additional bias into the data

[13:45:38] <akemot> hmm, thanks. As I thought, this metric is not that reliable

[13:46:44] <dstufft> akemot: I mean, even if it was limited to a single IP that's not reliable either :)

[13:48:36] <akemot> download stats are being collected per release, then I could simply take a mean value

[16:04:05] <mgedmin> is there a way to ask pip to upgrade everything I've installed in a virtualenv?

[16:10:08] <mgedmin> I wish pip wouldn't print tracebacks on ^C or -EPIPE

[16:10:46] <mgedmin> pip list -ol --format columns --exclude-editable | tail -n +3 | awk '{print $1}' | xargs -r pip install -U

[16:14:32] <mgedmin> hey, pip install --user -U <package> fails to upgrade outdated packages!

[16:15:13] <mgedmin> (only pip 10.0.0b2)

[16:16:01] <ngoldbaum> sounds like a bug you should report

[16:18:12] <dstufft> mgedmin: that first thing is a Python thing :(

[16:19:28] <mgedmin> yes, but pip could try/except and ignore please?

[16:30:54] <pr3d4t0r> Greetings.

[16:30:56] <pr3d4t0r> Q. What's missing? phi_rgateway-1.0.4-py2.py3-none-any.whl: does not contain PKGINFO, skipping - on devpi upload dist/*whl -- change: Python 3.6.5 under macOS High Sierra virtualenv and Debian Stretch standard Python 3.6.5 container. Thanks in advance.

[16:31:20] <pr3d4t0r> (sumanah indicated there was a discussion about this yesterday here, didn't see it until this morning.)

[17:31:04] <pr3d4t0r> Greetings again.

[17:32:17] <pr3d4t0r> I checked the .whl files from our 3.6.4 tool chain vs 3.6.5 and it looks like the later set up does not generate the metadata.json file -- how to overcome this? Not finding a lot of documentation about it. Thanks in advance.

[17:32:28] <pr3d4t0r> Same commands for the build.

[17:34:15] <pr3d4t0r> We build with: python setup.py bdist_wheel # python -> python3 in virtualenv

[17:34:19] <pr3d4t0r> Thanks in advance.

[17:36:01] <di_codes> pr3d4t0r: `metadata.json` was intentionally removed in `wheel==0.31.0`: <https://github.com/pypa/wheel/blob/e7b7541442992dea75455c6de37bfc2ead1b7c62/CHANGES.txt#L9>

[17:37:25] <ngoldbaum> https://github.com/pypa/wheel/issues/195

[17:37:37] <di_codes> pr3d4t0r: relevant devpi issue: <https://github.com/devpi/devpi/issues/524>

[17:48:25] <di_codes> pr3d4t0r: what version of `pkginfo` do you have? can you try running `pip install -U pkginfo`?

[17:54:33] <pr3d4t0r> di_codes: Reading - I was away from my workstation. Thank you.

[17:55:31] <pr3d4t0r> di_codes: pkginfo 1.4.2

[17:56:03] <pr3d4t0r> di_codes: There was no pkginfo in the 3.6.5 virtualenv, checking what I have on the 3.6.4 env.

[17:56:53] <pr3d4t0r> di_codes: Nothing there either, running the build again.

[18:05:44] <pr3d4t0r> di_codes: Trying to pin pkginfo - thanks.

[18:10:31] <pr3d4t0r> di_codes: Found it. devpi is installed outside the virtualenv, via Homebrew/Python 3.6.5 - the pkginfo there was 1.4.1. Fixed! Much appreciated.