Log file Viewer

[00:29:03] <ambv> jezdez: dstufft: ping? I have a Unicode-related pip problem (fix ready; needs high level approval)

[00:31:53] <dstufft> hi

[00:34:47] <ambv> dstufft: hi! lemme just finish a comment on github so you know what I'm talking about

[00:37:27] <ambv> dstufft: https://github.com/pypa/pip/pull/1473#issuecomment-46103338

[00:41:13] <dstufft> ambv: responded on ticket

[00:42:06] <ambv> if you ask mitsuhiko or anybody from Mercurial, they will say this is a Python 3-related bug at the moment ;-)

[00:42:16] <Ivo> ambv: where's your fix?

[00:43:01] <ambv> Ivo: I have it locally on my box, it basically reads egg-info as bytes, never trying to decode it

[00:43:17] <dstufft> if it doesn't work with Python 3 we can't use it as a fix

[00:43:19] <ambv> btw, this is the only usage of read_text_file in the entire pip codebase

[00:43:19] <Ivo> ambv: gist or pr it or smth

[00:44:52] <dstufft> I know how mitsuhiko feels about Python 3, but unless Python 3 changes AFAIK we *have* to treat Paths as unicode there, unless I'm wrong (am I?)

[00:45:55] <ambv> dstufft: this is why I asked here before proceeding with patching the entire thing

[00:46:28] <dstufft> sure :)

[00:46:33] <ambv> dstufft: if that is the case, shouldn't we unify and treat requirements from command-line as Unicode as well? being able to install a package directly but not as a dependency is a bug regardless

[00:46:34] <Ivo> biggest pain is pip has to deal with py2 byte strs, py2 encoded strs, py2 unicode, py3 str, py3 bytes... and then file streams in various modes :/

[00:46:51] <dstufft> ambv: yes we should treat things the same everywhere

[00:47:23] <dstufft> that's not the case right now i'm sure, but i'd consider those bugs

[00:48:26] <Ivo> ambv: biggest help would be a bare-example-package or two that demonstrates the problem, so we can easily reproduce

[00:49:59] <ambv> Ivo: that's easy, sure, can do that.

[00:51:41] <Ivo> ambv: something like what i did here https://github.com/pypa/pip/issues/3#issuecomment-42906232

[03:05:03] <ionelmc> gah!

[03:05:05] <ionelmc> setuptools must be installed to install from a source distribution

[07:57:51] <techtonik> hi

[07:58:05] <techtonik> is there any replacement for setup.py?

[07:58:18] <techtonik> i want to clean up the root of my project

[07:58:35] <techtonik> and place setup.py to the subdir

[07:58:47] <techtonik> with relative path to my package

[07:59:05] <techtonik> but setup.py doesn't seem to support relative package paths

[19:13:36] <jayd3e> so I have a my requirements txt setup with git+https urls in the form "-e git+https://username:pass@github.com/org/repo.git#egg=repo"

[19:14:05] <jayd3e> and I can't seem to push to them

[19:14:23] <jayd3e> like when I'm in that repo

[19:14:32] <jayd3e> after pip checks them out

[19:14:38] <jayd3e> clones* them

[19:14:59] <jayd3e> I get the error remote: Repository not found.

[19:15:06] <jayd3e> yet it can clone them successfully