Log file Viewer

[10:09:03] <mgedmin> whyzgeek, you can sort-of do this with some manual drudgery

[10:09:15] <mgedmin> be sure to use a buildout download cache

[10:09:34] <mgedmin> copy all the packages from it to some web server

[10:09:51] <mgedmin> then in your buildout.cfg do [buildout] find-links = http://your.intranet.server/packages

[10:10:14] <mgedmin> I tried collective.eggproxy the other day

[10:10:29] <mgedmin> gave up after it downloaded 600 megs of ancient lxml releases for random platforms I don't need

[10:10:32] <mgedmin> that took an hour

[10:10:40] <mgedmin> while my pip install lxml was standing still

[10:10:42] <mgedmin> so, not a fan

[10:11:26] <mgedmin> (the install didn't actually finish, I cancelled it after I saw it only fetched about half of the available versions)

[10:27:12] <schmir> pypiserver provides an easy way to run a private pypiserver, it also has a bit of functionality to update packages...(I'm the author)

[13:10:39] <goschtl> is it possible to access the buildout-configurations in my python module?

[13:10:58] <goschtl> for example i want to access this:

[13:11:02] <goschtl> [settings]

[13:11:06] <goschtl> port = 8888

[13:11:10] <goschtl> from my module

[13:34:45] <goschtl> J1m_: hi is it possible to access a section of my buildout.cfg for example [settings] port=8888 from my python module?

[13:55:26] <aclark> goschtl: sure if you open and read it with ConfigParser

[13:55:56] <goschtl> aclark: ok but it's not a *compiled version* then

[13:56:10] <aclark> goschtl: write a recipe or an extension

[13:56:27] <aclark> those are two ways to get access to that stuff when you run buildout… not sure that helps

[13:56:38] <aclark> buildout is not a runtime tool

[13:57:27] <goschtl> i think about using the buildout to configure some aspects of my app, and i don't want to double that in zope.conf product-configureation stuff

[13:58:26] <goschtl> maybe i write an extension which saves a *compiled version* of the configuration which i can access in my module?

[13:58:53] <goschtl> aclark: thanks for information

[14:00:50] <aclark> goschtl: sure or maybe you can parse .installed.cfg

[14:00:55] <aclark> which buildout saves after it runs

[14:01:06] <goschtl> ah ok i will have a look

[14:01:26] <schmir> I'd rather use a recipe that creates another config file for my app

[14:40:50] <mgedmin> that's the canonical way: have your buildout generate a config file for your app

[15:12:09] <goschtl> mgedmin: do they have a recipe for that?