Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
TurboGears
Home
+ new post
About this group
Join this group
Why update_config() in config.py won't add default paths to config if no modulename param?
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
seberino@spawar.navy.mil  
View profile  
 More options Nov 29 2006, 8:55 pm
From: "seber...@spawar.navy.mil" <seber...@spawar.navy.mil>
Date: Wed, 29 Nov 2006 17:55:25 -0800
Local: Wed, Nov 29 2006 8:55 pm
Subject: Why update_config() in config.py won't add default paths to config if no modulename param?
Print | Individual message | Show original | Report this message | Find messages by this author
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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Kevin Dangoor  
View profile  
 More options Dec 4 2006, 5:02 pm
From: Kevin Dangoor <dang...@gmail.com>
Date: Mon, 4 Dec 2006 17:02:42 -0500
Local: Mon, Dec 4 2006 5:02 pm
Subject: Re: [TurboGears] Why update_config() in config.py won't add default paths to config if no modulename param?
Print | Individual message | Show original | Report this message | Find messages by this author
On Nov 29, 2006, at 8:55 PM, seber...@spawar.navy.mil wrote:

> 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?? :)

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google