#jython IRC Log


IRC Log for 2014-09-22

Timestamps are in GMT/BST.

[6:33] -rajaniemi.freenode.net- *** Looking up your hostname...
[6:33] -rajaniemi.freenode.net- *** Checking Ident
[6:33] -rajaniemi.freenode.net- *** No Ident response
[6:33] -rajaniemi.freenode.net- *** Couldn't look up your hostname
[6:33] * JythonLogBot (~PircBot@ has joined #jython
[6:33] * Topic is 'Try Jython 2.7b3 at http://tinyurl.com/p2kmxod | This channel is logged: http://jython.extreme.st/irclogs/ | Please update the wiki: http://wiki.python.org/jython | Jython Book: http://jythonbook.com | Podcast: http://jython.org/jythonpodcast/'
[6:33] * Set by agronholm!~agronholm@2001:1bc8:102:6f29:ed9d:3487:3941:d41a on Fri Aug 22 22:40:30 UTC 2014
[8:01] * robbyoconnor (~wakawaka@guifications/user/r0bby) Quit (Quit: Konversation terminated!)
[8:02] * robbyoconnor (~wakawaka@guifications/user/r0bby) has joined #jython
[9:41] * choochter (choochter@nat/ibm/x-rpiigagbpdmtqivk) has joined #jython
[9:41] <choochter> morning folks... is there a process for raising PMR-equivalents against RedHat documented anywhere? [couldn't find anything on ltc.l.i.c and we seem to be hitting a kernel issue!]
[9:52] <choochter> sorry - wrong channel!! ;-(
[10:35] * a42niem (~niem@p578b7daf.dip0.t-ipconnect.de) Quit (Ping timeout: 244 seconds)
[12:27] * robbyoconnor (~wakawaka@guifications/user/r0bby) Quit (Excess Flood)
[12:27] * robbyoconnor (~wakawaka@guifications/user/r0bby) has joined #jython
[12:55] * xemdetia (xemdetia@nat/ibm/x-kqyvulgpyttixnfl) has joined #jython
[14:23] <jimbaker> nickmbailey, so there is this issue we have seen with twisted - https://twistedmatrix.com/trac/ticket/3413#comment:39
[14:23] <jimbaker> i haven't really haven't looked deeper than trying to run the unit tests, but it's been apparently **7** months since we did that, so it's worth re-evaluating
[14:41] <nickmbailey> jimbaker: heh, yeah i tracked it down to the DeprecatedAttribute stuff and just deleted that where it was causing issues
[14:41] <nickmbailey> but good to see it's known to twisted
[14:44] <nickmbailey> i also found an issue where the twisted select reactor passes set objects to jython's select method and jython complains that they objects aren't sequences
[14:45] <nickmbailey> i wonder if jython should just be checking for iterable rather than a sequence?
[14:45] <nickmbailey> offending line is https://hg.python.org/jython/file/3bfd14f0b231/Lib/_socket.py#l1405
[14:45] <nickmbailey> i changed twisted's select reactor to pass lists instead of sets and things worked better
[16:48] <jimbaker> nickmbailey, funny, there's some test for that
[16:48] <jimbaker> but clearly that test is overspecified. easy enough to fix
[16:48] <jimbaker> nickmbailey, so with those changes - how far do you get?
[16:48] <jimbaker> i guess it's time to look at that DeprecatedAttribute issue - it's just the sort of metaprogramming capability we pride ourselves in supporting in our compatibility :)
[17:03] <nickmbailey> jimbaker: with the fix to switch from sets to lists, things pretty much start working :)
[17:03] <jimbaker> nickmbailey, i think i should really prioritize that fix then :)
[17:03] <nickmbailey> at this point i'm working through the python libs with c deps my app currently uses as well as accidentally blocking the reactor with non twisted libs haha
[17:04] <jimbaker> nickmbailey, don't worry, that accidentally blocking the reactor is the common scourge. especially good when put into production
[17:05] <nickmbailey> haha
[17:06] <nickmbailey> just need to sprinkle in some deferToThread calls
[17:13] <jimbaker> nickmbailey, but of course, this is well known solution is never known to backfire ;)
[17:14] <jimbaker> anyway, this is really great stuff. please keep us posted. i will make that fix to trunk, and review DeprecatedAttribute so we can see what's going on and hopefully get trial running
[17:21] <nickmbailey> jimbaker: awesome! thanks
[17:32] <nickmbailey> jimbaker: oh i forgot I also had to hack twisted to not run this: http://twistedmatrix.com/trac/browser/tags/releases/twisted-14.0.0/twisted/internet/process.py#L83
[17:32] <nickmbailey> since jython doesn't implement os.pip()
[17:32] <nickmbailey> os.pipe()
[17:33] <jimbaker> nickmbailey, ack
[17:33] * maxb_ is now known as maxb
[18:42] * jorgew_ is now known as jorgew
[21:36] * xemdetia (xemdetia@nat/ibm/x-kqyvulgpyttixnfl) Quit (Ping timeout: 240 seconds)
[22:03] <jimbaker> paolo, about to check in a fix for socket, which probably fixes the issue you saw - this time i tested with what appears to be the cherrypy bug
[22:03] <jimbaker> that's a duplicate of django
[22:04] <jimbaker> the problem was that in socket cleanup - the last accepted child socket needs to shutdown the child thread pool. but it was not checking if the server socket was closed or not!
[22:04] <jimbaker> now it does
[22:04] <jimbaker> as of this fix i will now commit
[22:04] <jimbaker> agronholm, also, fixed the logging annoyance you mentioned
[22:05] <jimbaker> since i immediately saw it with cherrypy
[22:06] <paolo> jimbaker: thanks for the update, i'll check an report back
[22:07] <jimbaker> paolo, thanks!
[22:08] <paolo> jimbaker: is the patch already available somewhere?
[22:09] <jimbaker> will be in trunk in about 5 min
[22:09] <paolo> ok
[22:13] <jimbaker> paolo, pushed
[22:30] <paolo> jimbaker: for me your patch fixed #2201
[22:31] <paolo> django devserver works great now, i also tested with apache benchmark and everything was fine
[22:31] <paolo> :)
[22:32] <jimbaker> paolo, ok, i'm going to mark the relevant bugs as pending fixed
[22:32] <jimbaker> i usually close out a week later just to give other interested people a chance to respond
[22:32] <paolo> nice
[22:33] <jimbaker> and thanks again for your patience! it was a very easy fix once i realized what was going on. and it was somewhat linked to what i did earlier with respect to making sure stuff cleaned up properly
[22:34] <paolo> no problem really, and thanks for your efforts as well.
[22:57] <agronholm> jimbaker: hm, what was that? the socket thing?
[23:10] <jimbaker> agronholm, this is the debug logging in _socket
[23:11] <agronholm> ok
[23:11] <agronholm> thanks :)
[23:11] <jimbaker> i think i fixed it in your case. but i'm not a logging expert, but if it's not, there's probably just one line or two to add to what i did :)


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