[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