If you can run from source, please do ...

[sgmoore]

I hope this isn't off-topic, but it is prompted by this thread.

I have been running from source exclusively for several years without any problems, but have always been confused by the relationship between the installed version of calibre and the source.

I know that I am starting calibre using the exe's from the installed version, but these are tiny programs and probably just stubs, but does my 'run from source' need anything else from the installed version.

In particular what I usually do when a new version is released is

1) Exit Calibre
2) Download a new version
3) Refresh the source
4) Install the new version
5) Start Calibre.

In particular, I never install a new version without refreshing the source and I think I have only once refreshed the source without installing a new version.

Am I being over-cautious?

[ownedbycats]

If I understand you right, no. There are occasionally changes that require updating the binary when running from source (one example).

You may be interested in the alt-Friday beta releases.

[chaley]

Originally Posted by sgmoore

[...]
In particular, I never install a new version without refreshing the source and I think I have only once refreshed the source without installing a new version.

Am I being over-cautious?

Originally Posted by ownedbycats

If I understand you right, no. There are occasionally changes that require updating the binary when running from source (one example).

You may be interested in the alt-Friday beta releases.

Reinforcing @ownedbycats: it is very important that you use the latest calibre binary released before the source version you are running. The binaries contain a lot of stuff, for example the python interpreter, Qt, interfaces between python and system libraries, some hard-coded Qt styles, and many prerequisite system libraries. In some rare cases, running from source will fail because a new binary is required but doesn't yet exist.

It is also important that you update source while calibre is not running. If you don't then it is possible to end up running bits from each of the source releases.

I have to ask: why are you running from source if you don't refresh it to get access to new code until calibre is released?

[sgmoore]

Originally Posted by chaley

I have to ask: why are you running from source if you don't refresh it to get access to new code until calibre is released?

I have made some changes (personal hacks) to the source.

[JSWolf]

Originally Posted by sgmoore

I have made some changes (personal hacks) to the source.

Anything worth committing?

[ownedbycats]

'Personal' seems imply that they're, well, personal to this user.

[sgmoore]

Originally Posted by JSWolf

Anything worth committing?

Don't think so.

Also, whilst I am a programmer, I am most certainly not a Python programmer, so the code quality is pretty dire and I'm quite certain wouldn't get accepted.

[Terisa de morgan]

I don't know if it's related to this change but, after installing the beta, all the custom columns which use template functions and appear in book details are failing because of "Function not found". Going back to the official version has removed the error.

[chaley]

Originally Posted by Terisa de morgan

I don't know if it's related to this change but, after installing the beta, all the custom columns which use template functions and appear in book details are failing because of "Function not found". Going back to the official version has removed the error.

These are Python functions you wrote?

[ownedbycats]

My saved templates and custom Python functions all working as expected.

[Terisa de morgan]

Originally Posted by chaley

These are Python functions you wrote?

Yes, and no issue with them in the last release, only in the beta. You can see the error in the attached screen, and the number 1 is the result of the function (it must be stored, because it doesn't work in the template tester either).

I think the issue, again, is with the functions, as they don't appear in the template tester in the last release. I'm going to check if I find my issue (it's a plugin again, but a different one. Let's see if I find it).

[chaley]

Originally Posted by Terisa de morgan

Yes, and no issue with them in the last release, only in the beta.

I can't make it fail. I tried using these as the template in a composite column:

• program: a_stored_template()
• program: a_stored_function()
• {series: a_stored_function_needing_one_argument}

Both book_details displays always showed the correct output.

Can you give me any more details? For example:

• If you run in debug mode, do you get any output?
• Does it happen on startup or after you do something like change library?
• Is there anything unusual about the python functions? For example, do they call any other custom python functions?

[Terisa de morgan]

I'm going to check which plugin is messing with it (starting calibre without plugins keeps safe the python functions).

[ownedbycats]

I seem to recall another post with similar issues recently. I'm not having any success finding it though.

[chaley]

Originally Posted by Terisa de morgan

I'm going to check which plugin is messing with it (starting calibre without plugins keeps safe the python functions).

Thank you.

I think the problem can happen if you create your own Formatter() instance when the plugin is created, or if you make a copy of the the formatter functions dictionary. I'm not sure, though.

I am happy to help work out what is going wrong once you narrow it down.