Log file Viewer

[02:56:05] <bn_work> hi, pip 19.3.1, trying to do `pip install --upgrade google-api-python-client google-auth-httplib2 google-auth-oauthlib` and it finishes except I also noticed I got `ERROR: pyasn1-modules 0.2.8 has requirement pyasn1<0.5.0,>=0.4.6, but you'll have pyasn1 0.4.2 which is incompatible`, yet a few lines above it says `Requirement already satisfied, skipping upgrade: pyasn1>=0.1.3 in

[02:56:05] <bn_work> ./Library/Python/2.7/lib/python/site-packages (from rsa<4.6; python_version < "3.5"->google-auth>=1.16.0->google-api-python-client) (0.4.2)`. What gives?

[02:56:49] <bn_work> (note, this is (system?) python + pip on OSX 10.13.X)

[02:56:54] <bn_work> I think

[03:02:44] <bn_work> ok, forced it via `pip install --upgrade "pyasn1 <0.5.0,>=0.4.6"` but now I get `ERROR: awscli 1.14.61 has requirement PyYAML<=3.12,>=3.10, but you'll have pyyaml 5.1 which is incompatible.` ... sigh 😞

[08:56:28] <McSinyx[m]> bn_work, I hope I'm not too late to the party, but have you tried newer pip with --use-feature=2020-resolver which may find a compatible combination of packages

[14:15:47] <jmgb4> Anybody around? I am running into issues trying to make a new virtual environment, I am trying to figure out what https://bpa.st/6KYQ may mean

[14:17:48] <tos9> jmgb4: if this is the fedora? question someone asked yesterday (you presumably) it does mean that something has been broken in your python installation

[14:18:11] <tos9> I was unaware fedora had started breaking python installations too, usually it's just debian/ubuntu

[14:18:24] <tos9> but if that's the case now, look around for whatever packages fedora has split out -- presumably one that contains pip

[14:18:32] <jmgb4> Yeah it was me, For some reason I was getting disconnected every 30 seconds from irc and I gave up trying to get back on

[14:19:24] <jmgb4> It looks like python3-pip is the pip package for fedora

[14:19:50] <ngoldbaum> breaking python for fun and profit: the linux distro story

[14:20:01] <jmgb4> I second that

[14:21:53] <tos9> wait there's profit

[14:21:56] <tos9> damn. I'm in the wrong camp

[14:22:00] <jmgb4> lol

[14:22:00] <tos9> story of my life

[14:22:03] <ngoldbaum> breaking python for... reasons?

[14:23:02] <jmgb4> I am ready to just start making everything with sudo and call it a day

[14:23:07] <jmgb4> I have gone around in circles non stop

[14:24:18] <ngoldbaum> jmgb4: use pyenv

[14:24:28] <jmgb4> pyenv?

[14:24:36] <ngoldbaum> it’s almost always better to use a python install that lives in your home directory

[14:24:49] <ngoldbaum> https://github.com/pyenv/pyenv

[14:25:10] <ngoldbaum> don’t use the system python, use a python built by pyenv

[14:25:28] <ngoldbaum> also makes it much easier to switch python versions or manage multiple python installs

[14:27:26] <jmgb4> Its brew

[14:27:33] <jmgb4> even worse than running everything as root

[14:27:53] <ngoldbaum> why?

[14:28:00] <ngoldbaum> it avoids this problem, for example

[14:28:36] <jmgb4> brew? itsl ike snap

[14:28:38] <ngoldbaum> you also have zero chance of screwing up your OS

[14:28:42] <ngoldbaum> i know what brew is

[14:29:13] <ngoldbaum> pyenv doesn’t update things underneath you, if that’s what your concern is

[14:29:30] <jmgb4> Why not just use a prebuild for everything ? Why write your own code?

[14:29:37] <ngoldbaum> huh?

[14:29:42] <jmgb4> Thats kind of an extreme example but it removes the ability to do you

[14:30:09] <ngoldbaum> i think there might be a disconnect here, anyway good luck with your issue!

[14:30:33] <jmgb4> lol fair enough, Ill give it a shot

[14:31:26] <tos9> jmgb4: brew?

[14:31:31] <tos9> as in you're using linuxbrew?

[14:33:01] <ngoldbaum> no, they’re saying that pyenv is the “same” as brew and snap in some sense

[14:33:31] <tos9> oh

[14:36:01] <jmgb4> What? no

[14:36:14] <jmgb4> bew is the same as snap in a sense, not pyenv

[14:36:41] <jmgb4> Something is hosed though, its not my python

[14:36:54] <ngoldbaum> i guess “it’s brew” earlier wasn’t about pyenv?

[14:36:54] <jmgb4> I am getting all sorts of operation not permitted errors

[14:37:15] <jmgb4> That issue is out of scope for this channel. I should just nuke my machine and restart

[16:43:13] <skrblr> i'm running into an issue with the new pip resolver and extra constraints, trying to figure out if this is a known thing or if i'm wrong about how it should behave

[16:44:49] <skrblr> i have a constraints file with celery~=4.3.0, and trying to pip install -U --use-feature=2020-resolver -c constraints.txt celery[librabbitmq] fails with: "ERROR: Could not satisfy constraints for 'celery': installation from path or url cannot be constrained to a version"

[16:45:35] <skrblr> i guess my question is, with the new resolver, should all requirements with extras be pinned to a version in a requirements file and removed from constraints files?