Help! - Calibre 2.30 with OneDrive

[Stevex]

OK I have the variable
CALIBRE_CONFIG_DIRECTORY
set to
%OneDrive%\Calibre_Config
And the variable OneDrive set to
C:\Users\MyName\OneDrive
So till now this always worked very well
But on starting Calibre 2.30 I got the startup wizard and I found it is creating a new config directory here:
C:\Users\MyName\Desktop\%OneDrive%\Calibre_Config

Note that it is using literally %OneDrive% not substituting the string C:\Users\MyName\OneDrive

Help???!!! What is going on??? This setup has worked well for me for years.

[theducks]

Originally Posted by Stevex

OK I have the variable
CALIBRE_CONFIG_DIRECTORY
set to
%OneDrive%\Calibre_Config
And the variable OneDrive set to
C:\Users\MyName\OneDrive
So till now this always worked very well
But on starting Calibre 2.30 I got the startup wizard and I found it is creating a new config directory here:
C:\Users\MyName\Desktop\%OneDrive%\Calibre_Config

Note that it is using literally %OneDrive% not substituting the string C:\Users\MyName\OneDrive


Help???!!! What is going on??? This setup has worked well for me for years.

There is an update in 30 to address different cloud sync folders.

%reads and substitutes, the system environment setting for that variable%
This is the result I got, as I don't use One Drive (I have my own NAS)

C:\Users\Me>set %onedrive%
Environment variable C:\Users\Me\OneDrive not defined

There is a chance (small) that Kovid missed a use case


UPDATE
Wierd: when I look at the full output of SET

OneDrive=C:\Users\me\OneDrive

exists. But when I do set %OneDrive% (I tried camel case also), nada

[Stevex]

On 32 bit windows all ok
Just 64 bit windows, i get the problem
I’ll try to check it out a bit more later

[theducks]

Originally Posted by Stevex

On 32 bit windows all ok
Just 64 bit windows, i get the problem

I think this is a X64 problem, considering my failed test (on x64)

[kovidgoyal]

There haven't been any changes to how CALIBRE_CONFIG_DIRECTORY is processed in 3.30 and as far as I know it has never resolved environment variables, see https://github.com/kovidgoyal/calibr...stants.py#L236

So I am surprised it ever worked. As for why it stopped working in x64 it is probably because windows maintains a different set of env vars for 64bit and 32bit processes running on a 64bit computer -- I vaguely recall that windows jumps through various hoops for compatibility purposes when doing this.

[Stevex]

Hi Kovid

It all worked for me on x64 pc’s till now. The question is, what changed. I don’t know anything about python - is there any chance 3.30 installed a new python runtime? I just tried downgrading to 3.29 but that now doesn’t work either. Was all working 2 or 3 days ago.
Either windows changed or calibre changed or some ssl that calibre uses changed. Windows changing can be ruled out since the last update was second Tuesday in August.
Id like to track this down if poss...

Thanks for any quick ideas. In the meantime I changed the CALIBRE-CONFIG_DIRECTORY to be hardcoded but its not ideal

Ps I do understand if it’s just me you cant waste a lot of time but any ideas will help!

[kovidgoyal]

Nope 3.30 uses the same python as 3.29

[Stevex]

Ok thanks Kovid