#jython IRC Log

Index

IRC Log for 2013-12-02

Timestamps are in GMT/BST.

[0:25] * lheuer (~Adium@unaffiliated/lheuer) Quit (Ping timeout: 246 seconds)
[0:34] * Arfrever (~Arfrever@apache/committer/Arfrever) Quit (Ping timeout: 264 seconds)
[2:13] * also (uid1186@gateway/web/irccloud.com/x-hhsdiqqzqgcjsajw) has joined #jython
[3:38] * robbyoconnor (~wakawaka@guifications/user/r0bby) has joined #jython
[6:54] * lheuer (~Adium@unaffiliated/lheuer) has joined #jython
[7:27] * oscar_toro (~Thunderbi@80-62-162-242-static.dk.customer.tdc.net) has joined #jython
[7:52] * lheuer (~Adium@unaffiliated/lheuer) Quit (Ping timeout: 240 seconds)
[12:20] * vext01 (~edd@host-92-20-136-84.as13285.net) has joined #jython
[12:20] <vext01> jimbaker: knock knock?
[14:11] * robbyoconnor (~wakawaka@guifications/user/r0bby) Quit (Ping timeout: 245 seconds)
[14:14] * zz_whg is now known as whg
[15:15] * robbyoconnor (~wakawaka@guifications/user/r0bby) has joined #jython
[15:35] * robbyoconnor (~wakawaka@guifications/user/r0bby) Quit (Max SendQ exceeded)
[15:48] * enebo (~enebo@c-75-73-8-169.hsd1.mn.comcast.net) has joined #jython
[16:37] <jimbaker> vext01, hi!
[16:40] * Arfrever (~Arfrever@apache/committer/Arfrever) has joined #jython
[16:43] <vext01> jimbaker: hi
[16:43] <vext01> i was going to ask if the SSL stuff had been merged, but i think not
[16:43] <jimbaker> vext01, sadly no
[16:44] <jimbaker> vext01, we need to implement nonblocking SSL sockets, not just blocking, so that's more work
[16:44] <vext01> right
[16:44] <jimbaker> vext01, basically in the end jython-ssl is just a spike
[16:45] <jimbaker> topi`, vext01 - i looked at this problem some more, and i think we need to go with AsychronousSocketChannel, etc, in nio2, part of java 7
[16:46] <vext01> i also notice that i cant create a jython virtualenv using virtualenv running under cpython
[16:46] <vext01> so clarify, I installed virtualenv from my package manager -- i use it for cpython and pypy
[16:47] <jimbaker> the advantage of Async* is that we can build everything on a single underlying foundation, with blocking/timeouts layered on the underlying Async*
[16:47] <vext01> the virtualenv tool itself is run under cpython
[16:47] <vext01> if i do: virtualenv --python=/path/to/jython destdir
[16:47] <vext01> this will fail, whining about sys.prefix
[16:47] <jimbaker> vext01, my understanding, which may be completely wrong, is that virtualenv depends on the specific python implementation
[16:48] <jimbaker> but it sounds like --python has been added, but may not be compatible w/ jython
[16:48] <vext01> not sure about that
[16:48] <vext01> like i say it works for pypy and cpython
[16:48] <jimbaker> yeah, most likely virtualenv was extended to support pypy w/ --python
[16:48] <jimbaker> in the past, we only ran it under jython direclty
[16:49] <jimbaker> i don
[16:49] <jimbaker> don't see why sys.prefix should matter here
[16:50] <jimbaker> but i haven't tried --python just yet
[16:50] <vext01> oh my
[16:50] <jimbaker> (sys.prefix has a standard meaning??? maybe there are some other layout issues that don't work from some other python??? don't know)
[16:51] <vext01> im running virtualenv-1.7 (2011-11-30)
[16:51] <vext01> this could be the issue
[16:51] <vext01> time to update that port
[16:52] <jimbaker> vext01, ok, and please report back. i need to look at virtualenv directly myself - i think it has gotten more interesting in the latest versions, where more interesting could mean incompatibilities??? ;)
[16:52] <vext01> yep
[16:53] <vext01> this will be how I would install stuff into jython (once ssl works)
[16:59] <vext01> jimbaker: i updated virtualenv, same error
[16:59] <vext01> ERROR: The executable /home/edd/virtualenv/jython/bin/jython is not functioning
[16:59] <vext01> ERROR: It thinks sys.prefix is u'/usr/ports/mystuff/devel/py-virtualenv' (should be u'/home/edd/virtualenv/jython')
[16:59] <vext01> ERROR: virtualenv is not compatible with this system or executable
[17:00] <jimbaker> hmmm???. some problem w/ the jython startup script?
[17:00] <vext01> not sure
[17:02] <jimbaker> vext01, i will take a look at how sys.prefix is determined
[17:02] <vext01> nice one
[17:05] <jimbaker> topi`, so i don't know if you had a chance to look at SSLEngine in more detail, but i'm currently looking at this (before pausing last week for pausing for the last several days for the thanksgiving holiday we celebrate in the US)
[17:06] <jimbaker> i did demonstrate to my own satisfaction that making a blocking variant of Async* is totally trivial by using the Future API variant - simply block by using get on returned Futures
[17:08] <jimbaker> https://gist.github.com/jimbaker/7752779
[17:10] <jimbaker> what this means is that we can rid of all the complicated logic in current Lib/socket.py and readily allow users to move from blocking (including timeouts) to nonblocking per what is supported in cpython
[17:31] <jimbaker> vext01, i was looking at PySystemState.findRoot, which determines sys.rpefix, and i can safely say that the logic is ??? complex
[17:31] <vext01> hehe
[17:38] <vext01> prohibitively so?
[17:38] <jimbaker> vext01, no, i think it's decidable ;)
[17:38] <vext01> thanks for looking at this
[17:39] <jimbaker> vext01, i don't what dependency virtualenv has on pip??? my recent work has basically proceeded w/ the implication that getting pip working is central to any real jython 2.7
[17:40] <jimbaker> one thing i noticed w/ concern is that virtualenv bundles pip, which might mean any patch based on unicode could require working through its dev cycle too
[17:40] <jimbaker> in terms of getting stuff upstreamed
[17:41] <jimbaker> as far as i can tell, this is the only patch we require of pip once we have reasonable other infrastructure completed
[17:43] <jimbaker> oh well, just more branches to use until the upstreaming is completed :)
[17:44] <vext01> yeh it installs a bundled pip into the env
[17:44] <vext01> you can then use this to install into the virtualenv
[17:46] <jimbaker> vext01, which is sort of the point of a virtualenv ??? ;)
[17:47] <jimbaker> i suppose one can install one own's pip or use easy_install instead
[17:47] <jimbaker> right now i safely ignore these issues since i blow away my site-packages on a regular basis w/ ant clean
[17:48] <jimbaker> but must be addressed
[17:55] <vext01> it would be really sweet to use virtualenv with jython, like it were any other python implementation
[17:56] <vext01> but i take your point that you can use the source dir as a kind of "virtualenv"
[17:57] <jimbaker> vext01, yeah, we will get virtualenv working. it's a must
[17:57] <jimbaker> i'm just giving you options for now :)
[17:58] <vext01> cool
[17:59] * lheuer (~Adium@unaffiliated/lheuer) has joined #jython
[18:12] * enebo (~enebo@c-75-73-8-169.hsd1.mn.comcast.net) Quit (Quit: enebo)
[18:42] * paolo (~Paolo@net-37-117-0-21.cust.dsl.vodafone.it) has joined #jython
[18:47] <jimbaker> reading virtualenv's docs: Virtualenv's release schedule is tied to pip's -- each time there's a new pip release, there will be a new virtualenv release that bundles the new version of pip.
[18:47] <jimbaker> so this simplifies upstream mgmt significantly
[19:20] * lheuer (~Adium@unaffiliated/lheuer) Quit (Ping timeout: 246 seconds)
[19:27] * lheuer (~Adium@unaffiliated/lheuer) has joined #jython
[19:30] * enebo (~enebo@c-75-73-8-169.hsd1.mn.comcast.net) has joined #jython
[19:30] <vext01> that makes sense
[21:22] * Arfrever (~Arfrever@apache/committer/Arfrever) Quit (*.net *.split)
[22:16] * paolo (~Paolo@net-37-117-0-21.cust.dsl.vodafone.it) Quit (Quit: Leaving)
[22:31] * lheuer1 (~Adium@82.113.98.176) has joined #jython
[22:32] * lheuer (~Adium@unaffiliated/lheuer) Quit (Ping timeout: 272 seconds)
[23:33] * webskipper (~webskippe@91-64-7-0-dynip.superkabel.de) has joined #jython
[23:35] <webskipper> Does support Jython module "re" and module "subprocess" ?
[23:44] * enebo (~enebo@c-75-73-8-169.hsd1.mn.comcast.net) Quit (Quit: enebo)

Index

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