Log file Viewer

[08:39:55] <agronholm> I wonder how much python 2.6 is still being used

[08:40:02] <agronholm> seeing some statistics would be nice

[11:00:08] <unai> Any idea why pip 1.5.3 hangs with git submodules?

[11:01:06] <unai> Example: git+https://github.com/gitpython-developers/GitPython.git#egg=GitPython

[11:11:39] <apollo13> hmm, that library reminds me of the one I helped michael to write

[11:11:48] <apollo13> unai: works for me on pip 1.5.6

[11:12:40] <apollo13> oh lol it is a fork of what we started :)

[11:20:50] <nanonyme> apollo13, hmm?

[11:21:00] <nanonyme> Oh

[11:21:42] <nanonyme> Looks like its tests are failing, I wouldn't really install from master

[11:22:25] <apollo13> nanonyme: I was one of the earlier authors of that library (years ago)

[11:25:10] <nanonyme> Ah, at least the tests are not Python2.6-compatible

[11:25:26] <apollo13> dunno, I dropped it ages ago

[11:25:39] <nanonyme> Well, that project is running on Travis with 2.6

[11:25:43] <nanonyme> It's failing a lot there

[11:26:00] <nanonyme> It's failing a lot on 2.7 too though

[11:26:08] <apollo13> I don't know why you even care :þ

[11:26:39] <nanonyme> I care in that unai should probably stay far from GitPython if they can't even get their tests to pass ;)

[11:27:41] <nanonyme> https://github.com/libgit2/pygit2 might be a better call if the intention is just to use something with which you can use Git through Python

[11:29:43] <apollo13> certainly

[11:29:58] <apollo13> although when we wrote it libgit didn't exist at all :þ

[11:30:19] <apollo13> we actually forked and called git all the time :/

[11:30:41] <nanonyme> I'm aware libgit2 is pretty new, yes

[11:32:56] <nanonyme> apollo13, hmm, you mean fork+exec instead of just going through subprocess?

[11:33:21] <apollo13> nanonyme: subprocess, but isn't that the same?

[11:33:26] <apollo13> technically I mean

[11:33:58] <nanonyme> Well, on POSIX anyway

[11:34:29] <apollo13> there is something else?

[11:36:23] <nanonyme> CreateProcess?

[11:37:53] <apollo13> yeah, as I said ;)

[20:15:19] <xeno___> I am looking at http://rodmtech.net/docs/mezzanine/a-mezzanine-tutorial-take-2/#contents and I don't have a requirements directory at the point indicated, only a requirements.txt file.

[23:12:55] <phschwartz> Is it possible to run pip pragmatically without shelling out via subprocesses?

[23:20:28] <dstufft> phschwartz: theortically yes

[23:20:48] <dstufft> it's not exactly supported :) but it may work

[23:21:15] <dstufft> ``import pip; pip.main()`` is a fairly high level way of doing that by passing an argv into pip.main() w/o the subprocess

[23:24:27] <tomprince> Note that pip will create subprocesses as part of installing (if you aren't using wheels).