Re: xinclude and pathnames

2006-09-14 Thread Tim Arnold
"Fredrik Lundh" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Rob Williscroft wrote: > >> The default handler just sees the href value as a filename, so you >> should be able to use a relative path if you os.chdir() to the working >> directory before processing you xml file. > > an

Re: xinclude and pathnames

2006-09-14 Thread Fredrik Lundh
Rob Williscroft wrote: > The default handler just sees the href value as a filename, so you > should be able to use a relative path if you os.chdir() to the working > directory before processing you xml file. and if that's not good enough, writing a custom loader is trivial (see the default_load

Re: xinclude and pathnames

2006-09-14 Thread Rob Williscroft
Tim Arnold wrote in news:[EMAIL PROTECTED] in comp.lang.python: > "Tim Arnold" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] >> I'm using ElementTree to access some xml configuration files, and >> using the module's xinclude capability. I've got lines like this in >> the parent x

Re: xinclude and pathnames

2006-09-14 Thread Tim Arnold
"Tim Arnold" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > I'm using ElementTree to access some xml configuration files, and using > the module's xinclude capability. I've got lines like this in the parent > xml file (which lives in the same directory as the included xml file): >

xinclude and pathnames

2006-09-13 Thread Tim Arnold
I'm using ElementTree to access some xml configuration files, and using the module's xinclude capability. I've got lines like this in the parent xml file (which lives in the same directory as the included xml file): When I started the project it was Unix-only; this worked fine. Now I have user