Why update_config() in config.py won't add default paths to config if no modulename param?

14 views
Skip to first unread message

sebe...@spawar.navy.mil

unread,
Nov 29, 2006, 8:55:25 PM11/29/06
to TurboGears
I was looking at source of update_config in turbogears/config.py.

**ONLY** when a modulename param is passed does the config receive
standard default paths such as top_level_dir, package_dir &
current_dir_uri.

Can someone please explain, if they don't mind, why when NO modulename
param is passed does poor little config **NOT** get those nice paths
defined like top_level_dir, package_dir & current_dir_uri?? :)

Thanks,

Chris

Kevin Dangoor

unread,
Dec 4, 2006, 5:02:42 PM12/4/06
to turbo...@googlegroups.com

This is a fine question. top_level_dir and package_dir are both based
on the module specifically (they use the
pkg_resources.resource_filename which locates things relative to the
pythonpath).

current_dir_uri could be defined in all cases, though.

Kevin

Reply all
Reply to author
Forward
0 new messages