PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Wednesday the 22nd of July, 2015

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[00:01:36] <tchaypo> it seems that `tox -ejython` on setuptools is broken because of http://bugs.jython.org/issue2376
[00:07:31] <dstufft> a PR was merged a few days ago that I think fixes that
[00:07:50] <tchaypo> yep, i see a merge that matches the description on the issue
[00:19:37] <tchaypo> hrm. that PR doesn’t seem to have had any input from travis.. and on my machine it fails 5 tests
[00:19:56] <tchaypo> well, tip fails 5 tests. I don’t know whether the failures were introduced in that particular PR
[00:36:06] <tchaypo> okay, it looks like all 5 failures come from before that PR
[00:36:24] <tchaypo> let’s see how jython copes..
[00:44:01] <tchaypo> hrm.
[00:44:34] <tchaypo> so, I’ve got the tip of pip, with PR2978.
[00:45:00] <tchaypo> I’ve made a new virtualenv and used `pip install —upgrade .` to install the new pip in the virtualenv
[00:45:08] <tchaypo> but `tox -ejython` still failes
[00:45:11] <tchaypo> https://www.irccloud.com/pastebin/z76Y2cWJ/
[00:46:03] <tchaypo> I think this is because when tox makes .tox/jython, the pip it puts there is going to be the pip that’s bundled with virtualenv, not the pip in the ~/src/pip virtualenv
[00:46:43] <tchaypo> I guess the long way to fix that would be to build myself an sdist of a newer virtualenv that incorporates the newer pip and then install that into my virtualenv
[00:46:47] <tchaypo> *rocks quietly in the corner*
[01:43:32] <tchaypo> "Files in the virtualenv_embedded/ subdirectory are embedded into virtualenv.py itself as base64-encoded strings “ But of course.
[01:44:23] <tchaypo> (no really, of course it’s done that way, it just took me by surprise when I read it first)
[02:42:05] <tchaypo> of course jython-2.7.0/bin contains its own pip. Why wouldn’t I expect that?
[02:45:04] <tchaypo> okay, this is too hard. I’m going to write the new env marker implementation targeting cpython>=2.6 and just blindly assume that it’s going to work on jython. Hopefully by the time I have something to test, the jython ecosystem will have a functioning pip/virtualenv/setuptools again