[01:19:26] <dstufft> Alex_Gaynor: it won't break anything, it's self contained, but it might make distros mad at you right now as they have yet another thing to rm -rf until they figure out how to handle it
[01:19:44] <Alex_Gaynor> dstufft: That is definitely their problem
[01:19:57] <jimbaker> dstufft, in jython trunk soon - i'm hoping for next week to merge in my branch that fully supports ssl/select
[01:20:15] <dstufft> Alex_Gaynor: ok, then i'll try to make up a patch tonight
[01:20:16] <jimbaker> that basically gates beta 3 of jython
[01:20:22] <Alex_Gaynor> dstufft: <3 did I give you commit already?
[01:20:37] <dstufft> Alex_Gaynor: yea I think so, but I probably won't use it to commit this
[01:20:48] <jimbaker> which we can then give you a jar for
[01:20:51] <Alex_Gaynor> dstufft: you can do it in a branch, most of us just work in branches in the main repo
[01:22:28] <dstufft> https://github.com/yyuu/pyenv/tree/master/plugins/python-build/share/python-build things it supports
[01:22:56] <dstufft> I wonder if I know anyone who works on IronPython
[01:23:04] <dstufft> it'd be cool to get pip support everywhere
[01:23:23] <jimbaker> dstufft, ok looking at https://github.com/yyuu/pyenv/blob/master/plugins/python-build/share/python-build/jython-2.7-beta1, that's just doing maven central
[01:24:22] <dstufft> https://github.com/yyuu/pyenv/blob/master/plugins/python-build/share/python-build/jython-dev clone the repo and runs jython_builder, which uh looks like it uses ant
[01:25:45] <dstufft> jimbaker: So Jython itself still needs the ssl/select changes, is there any other changes in Jython that are required that you know of?
[01:32:54] <Alex_Gaynor> dstufft: ever figure out why the using a wheel thing caused problems?
[01:33:56] <dstufft> Alex_Gaynor: partially yes, some of it was we were testing for a setuptools .pth file to be updated, but it's a file that gets lazily created the first time you install something, and switching from setup.py develop to wheels meant that the file was no longer implicitly created as part of installing pip
[01:34:15] <dstufft> so our assertions against that file being updated were wrong
[01:34:28] <dstufft> because it was now created isntead of updated
[01:35:04] <dstufft> (In general i'm not sure it makes sense to differentiate between created and updated and we should instead be asserting that the file is in the state we expect it to be in, but that's a bigger change)
[03:29:27] <jimbaker> dstufft, i made a pull request with my change to html5lib - https://github.com/html5lib/html5lib-python/pull/150
[17:31:19] <pmxbot> Bumped to 3.5 in preparation for next release.
[17:31:19] <pmxbot> Added tag 3.5 for changeset 98f29d521c3a
[17:31:19] <pmxbot> Bumped to 3.6 in preparation for next release.
[21:21:41] <jaraco> dstufft, I see it'll take up to 15 minutes for my account to appear. That's fine, but what hostname should I use to connect to the host?
[21:21:56] <jaraco> I'm assuming the public facing name points to fastly and not the origin server.
[21:25:04] <dstufft> that's where it handles the cloning
[21:25:14] <jaraco> or it might just need to be enabled as a plugin
[21:26:19] <dstufft> jaraco: so my knowledge of hg concepts is pretty limited, how hard/bad would it be to switch from bookmarks to branches? I can probably get salt using bookmarks instead but if it's not hard/bad to just use branches that'd probably be easier (also it seems like bitbucket freaks out over bookmarks in ways)
[21:28:20] <jaraco> Using branches is the wrong model. It would require creating lots of extra commits in that branch, merging for every release, and it would be error-prone. It would also not be possible to easily reset the bookmark to an older version if necessary.
[21:32:15] <dstufft> jaraco: I'm gonna get an upgraded Mercurial on the boxes first I guess
[21:33:00] <jaraco> Cool. You can actually pip install mercurial to the system Python, but it sounds like your EPEL/salt model is much better for repeatability.
[21:33:42] <dstufft> salt can install from pip too
[21:36:14] <jaraco> Weird - the mercurial download page suggests using Fedora Projects EPEL. I find it strange that they would recommend a technique that results in such a stale version.
[21:36:25] <jaraco> Is it an old version of CentOS?
[21:36:26] <dstufft> Fedora and CentOS are different
[21:36:52] <dstufft> it's CentOS 6.5, but Fedora is the less old but more unstable stuff
[21:37:03] <EWDurbin> i've never gone searching for newer mercurials.
[21:37:29] <jaraco> They suggest "yum install '*mercurial*'"
[21:37:38] <jaraco> Was it installed with the asterixes?
[21:51:57] <EWDurbin> it should be - pkg.purged: mercurial-rpm
[21:52:06] <EWDurbin> since that's the state defined above that you need
[21:52:10] <dstufft> Invalid requisite type 'pkg.purged' in state 'mercurial', in SLS 'pkg.hg'. Requisite types must not contain dots, did you mean 'pkg'?
[21:52:20] <dstufft> maybe it should jsut be pkg: mercurial-rpm ?