PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Wednesday the 2nd of July, 2014

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[00:45:22] <pthiem> jaraco, are you available for a short bit for some brain picking?
[00:46:23] <jaraco> pthiem, now's a bad time - perhaps tomorrow or another day.
[00:46:44] <pthiem> no problem
[09:45:51] <xafer> dstufft, regarding your python3.3 issue I have the same: I've just tested https://gist.github.com/xavfernandez/81f4d3890933d15e6180 on a fresh Ubuntu 14.04 install with "success"
[09:49:37] <xafer> wanted to comment it on your SO question but I'm lacking reputation :-/
[13:07:34] <dstufft> xafer: ah right, i forgot you had the issue too
[13:14:35] <xafer> yup it's been two weeks that I've been planning to return to it without great hope but I'm glad you've got some core dev attention on it :)
[13:17:34] <dstufft> I'm seeing if I can repro yours on Ubuntu 14.04 right now
[13:17:47] <dstufft> if so that is good news, because I generally have not been able to repro mine on anything but travis
[13:20:51] <xafer> this morning I've installed a 14.04 server on virtual box and the bug was 100% reproducible
[13:21:46] <xafer> and got python 3.3.5 from deadsnakes
[13:39:12] <dstufft> xafer: added your instructions to the question
[13:39:24] <xafer> did you reproduce it ?
[13:41:01] <dstufft> yes
[13:41:09] <dstufft> I spun up a rackspace cloud server
[13:41:11] <xafer> great :)
[19:47:54] <dstufft> FML
[19:48:12] <dstufft> https://github.com/dstufft/pip/commit/7edf4c218b11b122977d584a43f9147ebfa4665b this might be the solution
[22:02:28] <xafer> dstufft, that's where I left my analysis last time: https://gist.github.com/xavfernandez/1ea7dc03d5dc793cd082 but no idea what could trigger this poll behavior change
[22:03:48] <dstufft> xafer: I've updated the question, I found something that seems to fix it, and i'm not sure why it fixes it
[22:06:27] <xafer> strange, like this whole issue :p
[22:34:05] <xafer> but calling super(CallbackFileWrapper, self).__del__() also fixes the stuck issue :s
[22:37:34] <dstufft> wat
[22:37:40] <dstufft> object() doesn't have a __del__ defined
[22:37:56] <dstufft> so that should print an traceback to stderr