#jython IRC Log (v0.9)

Index

IRC Log for 2013-07-12

Timestamps are in GMT/BST.

[0:48] * lheuer (~Adium@blfd-5d82003f.pool.mediaWays.net) has joined #jython
[2:06] * lheuer1 (~Adium@blfd-5d821cb2.pool.mediaWays.net) has joined #jython
[2:09] * lheuer (~Adium@blfd-5d82003f.pool.mediaWays.net) Quit (Ping timeout: 260 seconds)
[2:49] * lheuer1 (~Adium@blfd-5d821cb2.pool.mediaWays.net) Quit (Quit: Leaving.)
[5:32] * lheuer (~Adium@blfd-5d821cb2.pool.mediaWays.net) has joined #jython
[7:14] * seletz (~seletz@HSI-KBW-078-042-237-159.hsi3.kabel-badenwuerttemberg.de) has joined #jython
[7:26] * Arfrever (~Arfrever@apache/committer/Arfrever) has joined #jython
[7:30] * seletz (~seletz@HSI-KBW-078-042-237-159.hsi3.kabel-badenwuerttemberg.de) has left #jython
[7:40] * mcurve (~quassel@pop.nakinasystems.com) Quit (Ping timeout: 264 seconds)
[7:40] * mcurve_ (~quassel@pop.nakinasystems.com) has joined #jython
[7:46] * robbyoconnor (~wakawaka@guifications/user/r0bby) Quit (Ping timeout: 248 seconds)
[13:49] * enebo (~enebo@c-75-73-8-169.hsd1.mn.comcast.net) has joined #jython
[17:05] * mcurve_ (~quassel@pop.nakinasystems.com) Quit (Ping timeout: 246 seconds)
[17:05] * mcurve (~quassel@pop.nakinasystems.com) has joined #jython
[17:10] * lheuer (~Adium@blfd-5d821cb2.pool.mediaWays.net) Quit (Quit: Leaving.)
[17:22] * shashank1 (~shashank@208.91.2.2) Quit (Quit: Leaving.)
[17:22] * shashank (~shashank@208.91.2.2) has joined #jython
[17:51] * lheuer (~Adium@blfd-5d821cb2.pool.mediaWays.net) has joined #jython
[17:55] * paolo (~Paolo@81-174-15-73.v4.ngi.it) has joined #jython
[18:14] * paolo (~Paolo@81-174-15-73.v4.ngi.it) Quit (Quit: Leaving)
[18:58] * robbyoconnor (~wakawaka@guifications/user/r0bby) has joined #jython
[20:03] * ChanServ (ChanServ@services.) Quit (shutting down)
[20:07] * ChanServ (ChanServ@services.) has joined #jython
[22:20] * enebo (~enebo@c-75-73-8-169.hsd1.mn.comcast.net) Quit (Quit: enebo)
[22:58] * bgrz (~x@93-87-112-9.dynamic.isp.telekom.rs) has joined #jython
[22:58] * enebo (~enebo@c-75-73-8-169.hsd1.mn.comcast.net) has joined #jython
[23:02] <bgrz> anyone having this kind of problem with jython and setuptools: Couldn't find index page for 'package.name' (maybe misspelled?)
[23:03] <bgrz> I'm using 2.7b1, it used to work fine few weeks ago
[23:18] <jimbaker> bgrz, i've started looking at that problem. you're absolutely right in thinking it used to work :)
[23:18] <bgrz> jimbaker: what might be the cause?
[23:19] <bgrz> in other words, when can we expect the fix :D
[23:19] <jimbaker> pip now does ssl certificate verification; so does the underlying java for jython
[23:19] <jimbaker> but pip doesn't know this logic exists
[23:19] <bgrz> any workarounds?
[23:20] <jimbaker> bgrz, one would expect --insecure to work, but it doesn't in my testing
[23:20] <bgrz> ahh
[23:20] <jimbaker> anyway, i'll try to find a workaround and post here a fork of pip for others to test
[23:21] <jimbaker> should probably have something available today - i don't see anything that looks crazy
[23:21] <jimbaker> just need to understand pip's logic
[23:21] <bgrz> I'm not sure that'll solve my actual problem
[23:21] <bgrz> since I use zc.buildout actually
[23:21] <jimbaker> bgrz, i don't know zc.buildout - how does it rely on pip?
[23:21] <bgrz> it relies on setuptools
[23:22] <jimbaker> hmmm, different fix also applied by zc.buildout?
[23:22] <bgrz> pulls all packages that you declare in buildout.cfg and installs them locally
[23:23] <bgrz> don't know what you mean?
[23:23] <jimbaker> bgrz, sure - could you file a bug in bugs.jython.org with the exact steps to reproduce? this would help me take a look at this w/o having to understand buildout first
[23:24] <jimbaker> bgrz, what i mean is - there was a discussion a while back on man in the middle attacks in the packaging community
[23:24] <jimbaker> i believe there was a documented exploit
[23:24] <jimbaker> against python packaging
[23:24] <jimbaker> and this got people to start acting, vs talking :)
[23:25] <bgrz> yeah, something was substantially changed somewhere remotely in the last few weeks
[23:25] <bgrz> since I didn't touch that project's directory :)
[23:25] <jimbaker> no one actually tested this against jython, and i don't think we even thought of the issue, mostly because such exploits didn't apply to java
[23:26] <bgrz> so you suggest that I file a bug report for it?
[23:26] <jimbaker> anyway, just need to work through each affected tool and submit pull requests reversing this logic for jython
[23:26] <jimbaker> bgrz, that would be great!
[23:27] <bgrz> while I'm here, what is the state of jython code, should I stick to released 2.7b1, or could I jump to latest from source?
[23:27] <jimbaker> bgrz, might as well jump to trunk
[23:28] <jimbaker> it should be better than beta1 - we have a good regrtest
[23:28] <bgrz> that's cool
[23:28] <bgrz> thanks!
[23:28] <jimbaker> there's a chance i broke something you depend on because there's no test. but then again - that'd be great to know :)
[23:29] <jimbaker> the fix: add more tests
[23:29] <bgrz> can't be more broken than this :D
[23:30] <jimbaker> yeah, this part definitely sucks. i was ignoring it earlier, but now i actually something i want to run with jython that's annoying without pip support
[23:30] * jimbaker prefers working on compilers, not logic workarounds

Index

These logs were automatically created by JythonLogBot_ on irc.freenode.net using a slightly modified version of the Java IRC LogBot (github).