> My app should run on debian and windows platforms.
Hard lines :-(
> For storing the configuration data, I use the ConfigParser module.
> What I find difficult is to determine a place for my configuration
> file.
Config parser basically produces an .in file.
The rules that Windows uses to loca
On 8/3/06, Andre Roberge <[EMAIL PROTECTED]> wrote:
> On 8/3/06, Henry Finucane <[EMAIL PROTECTED]> wrote:
> > On 8/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > Hello!
> > >
> > > My app should run on debian and windows platforms. For storing the
> > > configuration data, I use the Con
On 8/3/06, Henry Finucane <[EMAIL PROTECTED]> wrote:
> On 8/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Hello!
> >
> > My app should run on debian and windows platforms. For storing the
> > configuration data, I use the ConfigParser module.
> >
> > What I find difficult is to determine
On 8/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hello!
>
> My app should run on debian and windows platforms. For storing the
> configuration data, I use the ConfigParser module.
>
> What I find difficult is to determine a place for my configuration file. On
> debian, it is simply
>
> o
Hello!
My app should run on debian and windows platforms. For storing the
configuration data, I use the ConfigParser module.
What I find difficult is to determine a place for my configuration file. On
debian, it is simply
os.path.join(os.path.expanduser("~")),"myconfig")
but what am I suppose
