«

Matthew Vernon a écrit :
> Hi,
>
> Is there a more idiomatic way of loading in a configuration file
> that's python code than:
>
> _temp=__import__(path,fromlist='cachestrs')
> cachestrs=_temp.cachestrs
>
> ? I mean, that's pretty ugly...Plain "import" doesn't work in this
> case because 'path' is a variable defined elsewhere

At least you have a way to do it, so you should be happy !-)

Another solution would be to add the path to sys.path, but it wouldn't
necessarily be the best thing to do here.

Hi,

Is there a more idiomatic way of loading in a configuration file
that's python code than:

_temp=__import__(path,fromlist='cachestrs')
cachestrs=_temp.cachestrs

? I mean, that's pretty ugly...Plain "import" doesn't work in this
case because 'path' is a variable defined elsewhere

TIA,

Matthew

--
Rapun.sel - outermost outpost of the Pick Empire
http://www.pick.ucam.org

Matthew Vernon wrote:

> Is there a more idiomatic way of loading in a configuration file
> that's python code than:
>
> _temp=__import__(path,fromlist='cachestrs')
> cachestrs=_temp.cachestrs
>
> ? I mean, that's pretty ugly...Plain "import" doesn't work in this
> case because 'path' is a variable defined elsewhere

execfile(path)

in a module with a fixed name that you can import wherever you need access
to your configuration data?

Peter

Peter Otten <__peter__@web.de> writes:

> Matthew Vernon wrote:
>
> > Is there a more idiomatic way of loading in a configuration file
> > that's python code than:
> >
> > _temp=__import__(path,fromlist='cachestrs')
> > cachestrs=_temp.cachestrs
> >
> > ? I mean, that's pretty ugly...Plain "import" doesn't work in this
> > case because 'path' is a variable defined elsewhere
>
> execfile(path)
>
> in a module with a fixed name that you can import wherever you need access
> to your configuration data?

That looks like what I want, thanks

Matthew

--
Rapun.sel - outermost outpost of the Pick Empire
http://www.pick.ucam.org

On 7/3/2010 5:15 AM, Matthew Vernon wrote:
> Hi,
>
> Is there a more idiomatic way of loading in a configuration file
> that's python code than:
>
> _temp=__import__(path,fromlist='cachestrs')
> cachestrs=_temp.cachestrs
>
> ? I mean, that's pretty ugly...Plain "import" doesn't work in this
> case because 'path' is a variable defined elsewhere

cachestrs=__import__(path,fromlist='cachestrs').ca chestrs
?

--
Terry Jan Reedy

In message <>, Matthew Vernon wrote:

> Is there a more idiomatic way of loading in a configuration file
> that's python code ...

Is it really a good idea to have a configuration language that’s Turing-
complete?

Ben Finney wrote:
> Lawrence D'Oliveiro <_zealand> writes:
>
>
>> In message <>, Matthew Vernon wrote:
>>
>>
>>> Is there a more idiomatic way of loading in a configuration file
>>> that's python code ...
>>>
>> Is it really a good idea to have a configuration language that’s Turing-
>> complete?
>>
>
> I think not. Configuration files should be read as data; they should be
> declarative only, not executable languages. That way, a different
> program can read and parse them without having to be a parser for an
> entire programming language.
>

For local non distributed applications, configuration files written in
python are just fine.

JM