Log file Viewer

[08:48:08] <codedecay> For some reason tonight my pip stopped copying binaries to /usr/local/bin. (Mac)

[08:48:19] <codedecay> anyone have an idea what I can do to fix it besides manually moving the files?

[08:59:29] <ztane> pypi went down a moment ago, back up again

[09:02:35] <ronny> codedecay: what version of pip?

[09:26:14] <busla> I´m trying to change a git repo (from original to a fork) in requirements.txt but am unable to override the already installed package when I deploy. Does anyone know if there is a "force upgrade" on a single package in requirements.txt?

[09:37:38] <tos9> codedecay: also what do you mean by copying? You mean creating binaries for things you're installing that specify `scripts` and things?

[09:37:56] <tos9> codedecay: (and for what ronny said, pastebin the full output of pip --version not just the version number)

[09:38:14] <tos9> busla: -U

[09:56:44] <busla> tos9: doesn´t that upgrade all packages?

[09:56:54] <tos9> busla: Yes.

[09:57:01] <tos9> (There's nothing in between unfortunately)

[09:57:47] <doismellburning> when in doubt, blow away the environment and install anew...

[09:58:24] <busla> tos9: I guess I could use --ignore-installed or —force-reinstall

[09:59:02] <busla> don´t understand the difference between those options though

[09:59:08] <busla> look the same to mee

[09:59:10] <busla> *me

[09:59:11] <tos9> busla: yes but you can't do that for just one thing

[09:59:20] <tos9> if you're specifying -r that's going to force reinstall everything

[09:59:43] <tos9> (also, you can't --force-reinstall without -U, which is really really annoying)

[10:00:35] <tos9> and yeah I forget what --ignore-installed's difference is, but try it

[10:00:54] <mgedmin> busla, change the version number (e.g. using a local version label) and require it in your requirements.txt?

[10:01:19] <mgedmin> e.g. verypackage >= 1.2+busla1

[10:01:22] <busla> mgedmin: it´s a git repo that I I need to swap out

[10:01:25] <tos9> well, if it's git it doesn't matter what the version number is

[10:01:36] <tos9> it's going to be installed again unless it's already installed.

[10:01:36] <busla> right

[10:01:57] <busla> it´s already installed, and I need to override it

[10:01:58] <mgedmin> yes, so? your fork will be version 1.2+busla1 in its setup py, but the installed version won't be -- and I would expect pip to go fetch it from the git url

[10:02:25] <tos9> mgedmin: pip will always go fetch it from the git URL

[10:02:37] <tos9> (even if you specify a version, because it doesn't know how versions correspond to git commits)

[10:03:06] <tos9> busla: right so, you have a requirements file, and you want to upgrade one thing in it to a new version, but not anything else in it that's not pinned?

[10:03:24] <busla> tos9: correct. I get Requirement already satisfied (use --upgrade to upgrade)

[10:03:28] <ionelmc> tos9: ready for your talk?

[10:03:42] <tos9> busla: then the only thing is -U with explicitly listing your thing as an argument

[10:03:44] <tos9> ionelmc: "maybe" :(

[10:03:51] <tos9> my slides are ... OK

[10:04:05] <tos9> so yeah I'm ready, not completely happy with it but hopefully it breeds some discussion / questions / thought

[10:04:21] <tos9> ionelmc: Are you in here :)?

[10:04:57] <busla> tos9: something like "pip install -r —upgrade git+http://github.com/busla/my-repo/#egg=my-repo ?

[10:05:13] <tos9> busla: No -r, but yep. If you don't want your dependencies even of that one package upgraded you'll need --no-deps too

[10:08:28] <codedecay> toss sorry went to the store. output is: pip 7.1.0 from /usr/local/lib/python2.7/site-packages (python 2.7)

[10:10:25] <busla> tos9: well, it´s a requirements.txt file that I want to deploy

[10:10:44] <tos9> busla: There's no way to do that.

[10:11:02] <tos9> It's all or nothing.

[10:11:21] <busla> tos9: ok, I could use —ignore-reinstalled in my elastic-beanstalk config then

[10:11:37] <busla> * —ignore-installed

[10:11:43] <tos9> busla: That's still "all" -- it's going to reinstall everything in your requirements file.

[10:12:13] <mgedmin> (and running pip install -r ... with no extra flags)

[10:14:29] <busla> mgedmin: can I specify an arbitrary version number for git repos?

[10:15:03] <mgedmin> it never occurred to me that you might not be able to?

[10:15:24] <mgedmin> iirc pip freeze produces git urls with an explicit commit hash

[10:15:45] <mgedmin> which would be an alternative if version numbers turned out not to work somehow

[10:17:40] <busla> mgedmin: ahh I see, so I can install a specific commit in requirements.txt?

[10:18:06] <mgedmin> I sure hope so, otherwise pip freeze would be lying to me :)

[10:18:12] <busla> mgedmin: found it

[10:18:13] <busla> https://pip.pypa.io/en/latest/reference/pip_install.html#git

[10:18:14] <busla> :-)

[10:19:44] <busla> mgedmin: nee, I get "Requirement already satisfied"

[14:48:32] <hashar> hello there :)

[14:48:52] <hashar> I was wondering if we could get pip to install matching requirements from site-package if they are present

[14:48:59] <hashar> to save some pypi downloads

[14:49:24] <hashar> without providing the whole site package though

[14:59:13] <ronny> hashar: unlikely to be done sanely with the current mechanisms, it would be doable if there was something like a repository of unpacked wheels

[14:59:21] <ronny> but its tricky to build such a thing

[14:59:27] <hashar> I can imagine

[14:59:46] <hashar> my use case was to avoid having to recompile native modules over and over on a Jenkins setup

[14:59:52] <hashar> but one of user told me about pip caching wheel

[14:59:57] <hashar> that seems to cover my use case :-}

[15:04:18] <ronny> yes, recent pip solves it way more nice

[15:04:36] <ronny> bbl