pmxbot IRC Log Viewer

[20:40:57] <cob> hi again, i've been strugling with buildout. I've tried several variations for getting a development environment going.

[20:41:36] <cob> I solved many things, but I'm stuck on a develop-eggs issue

[20:42:17] <cob> somehow the develop-eggs links aren't getting included in the pythonpath

[20:42:34] <cob> I'm using mr.develop recipe btw

[20:44:46] <cob> I've dug around extensively, for the past 3 days I've been tinkering with zc.buildout, and I'm afraid I'll have to scrap it if I can't get it to work

[20:57:18] <J1m> cob, I'm not familiar with mr.develop.

[20:57:49] <J1m> normally, you list some directories in the buildout develop option, which gets them built.

[20:58:23] <J1m> Then you *also* need to list the projects in the eggs options (or in dependencies) of scripts you're building.

[21:06:20] <cob> okay, I managed to get the import going, thanks.

[21:08:40] <cob> explicit, everything must be explicit I'm guessing... wonder what mr.developer's activate and deactivate is used for

[21:11:38] <hannosch> cob: mr.developer de/activate only takes effect after you run bin/buildout or bin/develop rb again

[21:11:48] <cob> yes, I was doing that

[21:12:04] <cob> oh, I'll try the develop rb bit

[21:12:16] <hannosch> with it, you shouldn't have to manage develop-eggs on your own

[21:12:37] <hannosch> but you still need to put stuff into eggs where you want it

[21:13:18] <cob> you mean the eggs= directive?

[21:13:22] <hannosch> yep

[21:13:25] <cob> okay

[21:13:59] <hannosch> de/activate puts stuff onto or removes it from the develop-eggs list

[21:14:13] <cob> what's that list good for?

[21:14:36] <hannosch> you either use a release of a package or a local development version

[21:15:31] <cob> oh I see, meaning it would switch the path buildout generates between a packed egg or an develop one

[21:15:42] <hannosch> mr.developer is mainly useful if you use released versions of some packages most of the time, but then once in a while you want a source checkout of them for a bit

[21:16:18] <cob> yes, I'm trying to organize an old site into repo, and another bit of code that I want to contribute to, along with my own site

[21:16:22] <hannosch> yep. and since you tell it where to find the source code of a package, you can run bin/develop checkout <somename>

[21:17:59] <cob> oh man, I spent hours searching for some info on that... either i missed it or it's just not there

[21:18:22] <hannosch> probably it's not there ;)

[21:18:35] <cob> i have another little problem, would you mind?

[21:18:48] <cob> it's to do with virtualenv

[21:18:57] <hannosch> IRC rule number 1: don't ask to ask :)

[21:19:04] <cob> yes, I know that one :)

[21:19:44] <hannosch> so just ask away. maybe I know something and can answer it. maybe someone else reads your real question

[21:19:48] <cob> anyway... I get a problem when I try to start a virtual env, and try to build my own [python]

[21:20:07] <cob> I've tried a few permutations

[21:20:57] <cob> the only way I can get a virtualenv to work is getting it started before any bootstrapping or buildout

[21:21:38] <hannosch> why do you want to use virtualenv and buildout at the same time?

[21:21:49] <cob> should I call my own [python] something else, because when buildout goes about trying to link python in there, the file is busy

[21:22:26] <cob> well, for one because I might not be able to install packages globally

[21:22:36] <jonathanu> include-site-packages = false is a great discovery

[21:22:48] <cob> when I start bootstrapping distutils bootstrapping bails with a permissions error

[21:22:55] <hannosch> buildout won't install anything globally either

[21:23:14] <cob> sorry, distribute

[21:23:19] <cob> not distutils

[21:23:20] <hannosch> ah, the dreaded distribute bootstrapping

[21:23:50] <hannosch> ok. in that case either install distribute once globally if you can

[21:24:09] <cob> okay, yes I can...

[21:24:11] <hannosch> or create a virtualenv, and then use the bin/python from the virtualenv to call bootstrap

[21:24:32] <cob> I was going to try a deploying from standard ubuntu AMI on AWS

[21:24:50] <cob> but I guess I need to customize no matter what

[21:25:26] <hannosch> yeah. unfortunately ubuntu has been rather creative. there's even more extra weirdness there regarding Python packaging

[21:27:11] <cob> thanks, I'm going to go try again with the extra eggs= without venv

[21:27:33] <cob> on a "custom" python install

[21:28:35] <hannosch> yeah. ubuntu uses Python itself for many OS tasks. so the system Python has a whole lot of stuff installed and is configured in special ways

[21:29:43] <cob> i'm just trying to make it easy for the other 10 guys that could work on this

[21:30:26] <cob> I'm wondering how many will try to use windows

[21:31:00] <hannosch> most of this should work on Windows. it's not tested as well, but in general it should all work

[21:36:22] <cob> do you do anything on AWS? I'm still thinking about my custom load balancer

[21:36:46] <cob> for monitoring load and firing up instances and shutting them down

[21:39:00] <cob> I'd probably prefer using rackspace, but that's not up to me

[21:40:38] <hannosch> I'm luckily just deferring all hosting stuff to our ops and infrastructure teams these days :)

[21:47:27] <cob> i'm on evil devops, I wish I could push this off to someone else, but there are few people who can understand this stuff these days... I even only half understand

Log file Viewer

Help | Karma | Search:

#buildout logs for Thursday the 27th of September, 2012