[07:29:36] <pombreda> I guess this may come handy? github.com/sarugaku/pythonfinder but techalchemy there is a chicken and egg problem: this is written in Python itself :|
[07:35:00] <pombreda> Windows is a totally different universe :|
[07:35:18] <pombreda> (in saying that I am trying to stay polite ;) )
[08:06:29] <njs> pombreda: for a standalone app targeted at folks who aren't necessarily python devs, then bundling is usually the best bet
[08:15:36] <pombreda> njs: thanks. I guess that the way to go too. Anything else looks like a source of problems at any deployment scale
[13:16:30] <ngoldbaum> (not that you necessarily want to do that)
[13:43:34] <pombreda> ngoldbaum: I probably would not want that layer of extra dependencies!
[13:59:52] <pombreda> hum, is activate_this.py gone in Python 3?
[14:00:46] <pombreda> shrikes. that's venv not virtualenv now
[14:46:57] <techalchemy> pombreda: i mean I assume you do have python, that library just finds _all_ of the installations (provided they are discoverable)
[16:11:18] <pombreda> techalchemy: the problem is mostly on Windows... the locations of installed Python are a bit messy and all over. So you may not even know whcih one to use to run the search ;)
[16:11:32] <techalchemy> pombreda: it doens't really matter which one you use
[16:12:20] <pombreda> techalchemy: here is my scenario: unzip an archive that contains a .bat script to boostrap. (and then installs and configures things)
[16:12:38] <techalchemy> the only thing I haven't updated pythonfinder to accommodate is windows store based installs... but the intention there is that they would be your primary / only python install and on your path anyway so it'd find that
[16:12:41] <pombreda> techalchemy: I do not know where or if there is an interpreter installed
[16:13:00] <pombreda> (and by default it is not in the path)
[16:13:40] <pombreda> so for now, I have instructed users to install Python 2.7 in the default location. (C:\Python27)
[16:13:41] <techalchemy> well I mean in theory it could be literally anywhere so your search parameters are a bit wide
[16:14:40] <pombreda> techalchemy: I think that in my case (which is an app) the only sane way as we are porting to Python 3 will be to bundle a whole interpreter (as njs suggested)
[16:17:57] <pombreda> techalchemy: there is nothing special on a Windows python, right? I could just rezip the install directory (and in my case I surely do not want to update the registery with .py extensions and such )
[16:18:21] <techalchemy> oh there are special things
[16:18:39] <pombreda> I wonder if I could likely install in one place and then repack for my bundle?