MobileRead Forums - View Single Post

fetihif112 · 09-23-2024, 11:42 PM

Hello, I have a small problem unrelated to the AO3 issue.

First of all, judging by the monthly release dates, is version 4.38 supposed to be the most recent one on PyPI? Because it isn't, it's still at 4.37.

I'm on Fedora 39, running Calibre 7.3.0, Python 3.12.6. Apparently, the Calibre plugin can use files from the CLI installation when you have both installed. That causes problems when the versions are different - specifically Calibre version 4.38 with CLI version 4.37 breaks downloading from Calibre. Other times in the past everything must have worked fine without me noticing. In this case, I assume it's about the new 4.38 searching feature: all URLs (from various sites, existing in the library or not) fail with error "module 'fanficfare.adapters' has no attribute 'get_url_search'". Uninstalling the CLI version and restarting Calibre fixes this. Reinstalling the CLI version and restarting Calibre breaks it again. Reinstalling 4.38 from within Calibre doesn't help as long as CLI 4.37 exists. I've tried multiple times, and these observations have been consistent.

I've had some trouble diagnosing this, but i'm 95% sure this is it. When all jobs instantly fail, the usual logs in the Jobs window are unavailable, so I had to use debug mode. Even in debug mode, the logs say "Successfully initialized third party plugins: FanFicFare (4, 38, 0)" and "FFF: DEBUG: 2024-09-24 05:58:40,116: calibre_plugins.fanficfare_plugin.fff_plugin(1140) : FanFicFare v4.38.0", with no indication of 4.37's presence other than the errors. I've looked at pip's install/uninstall process, and it doesn't touch any dependencies.

That in and of itself is not a big deal, reinstalling the CLI version whenever I need it takes seconds, but for correctness' sake, how would I go about having Calibre always prioritize its "natiive" version? If it involves error-prone messing with env/path stuff, which I'm unfamiliar with, is there some way of verifying from within Calibre what files it tries to load from where and make troubleshooting easier?

09-23-2024, 11:42 PM	#9968
fetihif112 Junior Member Posts: 1 Karma: 10 Join Date: Dec 2023 Device: none	Hello, I have a small problem unrelated to the AO3 issue. First of all, judging by the monthly release dates, is version 4.38 supposed to be the most recent one on PyPI? Because it isn't, it's still at 4.37. I'm on Fedora 39, running Calibre 7.3.0, Python 3.12.6. Apparently, the Calibre plugin can use files from the CLI installation when you have both installed. That causes problems when the versions are different - specifically Calibre version 4.38 with CLI version 4.37 breaks downloading from Calibre. Other times in the past everything must have worked fine without me noticing. In this case, I assume it's about the new 4.38 searching feature: all URLs (from various sites, existing in the library or not) fail with error "module 'fanficfare.adapters' has no attribute 'get_url_search'". Uninstalling the CLI version and restarting Calibre fixes this. Reinstalling the CLI version and restarting Calibre breaks it again. Reinstalling 4.38 from within Calibre doesn't help as long as CLI 4.37 exists. I've tried multiple times, and these observations have been consistent. I've had some trouble diagnosing this, but i'm 95% sure this is it. When all jobs instantly fail, the usual logs in the Jobs window are unavailable, so I had to use debug mode. Even in debug mode, the logs say "Successfully initialized third party plugins: FanFicFare (4, 38, 0)" and "FFF: DEBUG: 2024-09-24 05:58:40,116: calibre_plugins.fanficfare_plugin.fff_plugin(1140) : FanFicFare v4.38.0", with no indication of 4.37's presence other than the errors. I've looked at pip's install/uninstall process, and it doesn't touch any dependencies. That in and of itself is not a big deal, reinstalling the CLI version whenever I need it takes seconds, but for correctness' sake, how would I go about having Calibre always prioritize its "natiive" version? If it involves error-prone messing with env/path stuff, which I'm unfamiliar with, is there some way of verifying from within Calibre what files it tries to load from where and make troubleshooting easier?