On Thu, 05 Aug 2010 18:32:56 -0000
Rob Keeney <email address hidden> wrote:
> After additional testing I found the following:
>
> * ..\Documents\etc. does *not* work to write the file to correct location (path does not exist: E:\Documents\Documents\Web Site)
> * ..\..\Documents\etc. *does* work for opening file for the first time. However, the number of ..\ repetitions needs to match the level of the .leo file. I suppose this is the reason I had trouble with one file as the .leo file was 3 directory levels removed from the root, therefore needed ..\..\..\Documents\etc. to work properly.
Yep, that's all as it should be, the .. forms have been working correctly all along.
> This means that I have a workable temporary solution as long as I match
> the ..\ repetitions to the location of the .leo file (at least that's
> not subject to change).
Yep.
> I saw your note about the open python bug, very interesting. Any idea if
> this is still an issue with python3k?
It's listed as affecting all current versions and being still open, so yes. Basically they're stuck because the concept of 'absolute path' wasn't clearly thought through for Windows in the first place, and now they can't change the behavior of the function without breaking a lot of existing code.
On Thu, 05 Aug 2010 18:32:56 -0000
Rob Keeney <email address hidden> wrote:
> After additional testing I found the following: Documents\ Web Site) \etc. *does* work for opening file for the first time. However, the number of ..\ repetitions needs to match the level of the .leo file. I suppose this is the reason I had trouble with one file as the .leo file was 3 directory levels removed from the root, therefore needed ..\..\. .\Documents\ etc. to work properly.
>
> * ..\Documents\etc. does *not* work to write the file to correct location (path does not exist: E:\Documents\
> * ..\..\Documents
Yep, that's all as it should be, the .. forms have been working correctly all along.
> This means that I have a workable temporary solution as long as I match
> the ..\ repetitions to the location of the .leo file (at least that's
> not subject to change).
Yep.
> I saw your note about the open python bug, very interesting. Any idea if
> this is still an issue with python3k?
It's listed as affecting all current versions and being still open, so yes. Basically they're stuck because the concept of 'absolute path' wasn't clearly thought through for Windows in the first place, and now they can't change the behavior of the function without breaking a lot of existing code.