[01:39] <jrwren> greg-g: i'm gonna be opposite of rick_h_ and say - don't use venvs. use debs :)
[01:40] <jrwren> greg-g: so yeah, just whip up python use python system packages from ubuntu.
[01:40] <jrwren> greg-g: you on debian? then I can't help :p
[01:40] <jrwren> greg-g: ubuntu has nice python packages, and if it is missing 1 or 2, I can usually package them up in no time.
[01:41] <cmaloney> evening
[01:42] <cmaloney> venvs atre awesome
[01:42] <cmaloney> some commands i write a wrapper to execute
[01:48] <jrwren> venvs are a crutch for the weak :p
[02:09] <greg-g> jrwren: cmaloney this is what another buddy recommended: http://paste.debian.net/160032/
[02:09] <greg-g> venv's, basically
[02:09] <greg-g> he followed up with:
[02:09] <greg-g> 00:50 < paulprote> If you want a less heavy-handed way, but similarly  effective and more standard, you can make a 'setup.py'  that lists the packages *without* version numbers, and  './bin/pip install --editable . ' and 'bin/pip freeze  > requirements.txt'
[02:09] <greg-g> 00:50 < paulprote> Yeah I think that's better but now I have confused you  by making two suggestions oops.
[02:12] <jrwren> greg-g: so... why would you do that if your goal is to whip up a quick python script.
[02:12] <jrwren> greg-g: if you are starting some big ass project, sure.
[02:13] <jrwren> but if you are just whipping some up script????
[02:13] <greg-g> use case: writing a report generator from our phabricator install
[02:13] <greg-g> it might evolve over time, but yeah, light weight mostly
[02:14] <greg-g> the annoying bit before was when i switched from one laptop to another and it didn't work due to missing dependencies etc (ubuntu vs debian)
[02:14] <greg-g> (and I want others to maybe use it, others in our org, that is)
[02:19] <_stink_> i always make a virtualenv for a new thing, no matter the size.
[02:20] <_stink_> jrwren: take that!
[02:20] <greg-g> :)
[02:20] <_stink_> i do keep a generic virtualenv with ipython and requests, maybe simplejson installed for testing and such
[02:20] <jrwren> i used to, then i realized, I was being stupid.
[02:20] <_stink_> that i *might* use for really simple stuff
[02:20] <_stink_> haha
[02:21] <jrwren> greg-g: so... sharing python code sucks becuase all your uses will either need to create a venv and install all the deps, or install all the system deps.
[02:22] <greg-g> jrwren: isn't that what the ./bin/pip install -r requirements.txt step does for them?
[02:22] <greg-g> doesn't that make it easy for them to get the right dependencies?
[02:22] <jrwren> greg-g: yes
[02:22] <jrwren> for some def of "easy"
[02:23]  * greg-g is honstly trying to figure it out
[02:23] <jrwren> if you use any modules which are C, then you also need a build env and any c libs that those modules need.
[02:23] <jrwren> it can be a pain compared ot "just apt-get install these pkgs"
[02:23] <greg-g> I doubt C will come into my little report generator :)
[02:23] <greg-g> sure
[02:23] <jrwren> dunno.
[02:23] <jrwren> gonna use a DB?
[02:23] <jrwren> psycopg2? :)
[02:24] <greg-g> nope, it's a one time run thing
[02:24] <_stink_> another reason i like virtualenvs every time is because i frequently run old LTS installs, and i can get new libs from pypi
[02:24] <greg-g> the main dependency: https://github.com/disqus/python-phabricator
[02:24] <greg-g> alright, almost to my bus stop, thanks you two
[02:24] <greg-g> friday starts.... now.
[02:25] <jrwren> gl
[02:25]  * _stink_ puts on the techno
[02:25] <jrwren> apt-cache search says greg-g will be using venvs and pip :)
[02:25] <_stink_> hehe
[02:45] <rick_h_> greg-g: so it depends on what this is for. if it's something you use on your system a lot I just sudo pip install
[02:45] <rick_h_> greg-g: so httpie, some python tools for vim, etc I always just system install
[02:45] <rick_h_> greg-g: if it's something more experimental then yea, I'll venv it in ~/src/xxx
[02:45] <rick_h_> greg-g: and if it's really big/hairy/etc I'll say just whip up an lxc and system install it in there
[02:46] <rick_h_> but then you're an ssh away from using it each time
[02:46] <rick_h_> and yea, avoid python system packages unless it's somethig production and you can wait 6mo for an update
[02:47] <rick_h_> and are willing to run non-LTS packages
[02:50] <greg-g> :)
[02:54] <jrwren> <3 system packages.
[02:54] <jrwren> instant deploy FTW
[02:54] <rick_h_> I love them too
[02:54] <rick_h_> but find them to not work out well for fast moving things like libraries to things like clouds/etc that don't fall under "I can wait for next release" and "synced with distro release" schedules
[03:11] <cmaloney> Yeah, I'm with rick_h_ on this
[03:11] <cmaloney> if it's something like jedi where I need it over multiple projects, or something I use often then it gets sudo pip install ..
[03:12] <cmaloney> other things like galileo (libfitbit) get venvs with scripts
[03:12] <jrwren> hrm... for all my smack talk about system packages, I built a venv for flexget just last night.