Plugin index - entry not included in calibre list

Lakis · 06-23-2026, 02:07 PM

One of the mods added my plugin to the index (post is here), but so far (it's over a week) it's not visible in the calibre plugins' list. I'm thinking, if it's something in my plugin's structure or something else.
On my side I was thinking, if version and plugin name in side file (consts.py, then imported to __init__.py and used in Source class) are making any problems for the Plugin updater to read required data and it skips it or is it something else.

theducks · 06-23-2026, 02:52 PM

I looked at the Index of plugins and see the entry (code) and did not spot why it is not being scraped to include in the Get Plugins list (also deal with updates).

The name in the init is not what is used for the list.

Comfy.n · 06-23-2026, 04:43 PM

I found that splitting the imports makes the parser happy:

from calibre_plugins.wolnelektury_source.consts import PLUGIN_VERSION
from calibre_plugins.wolnelektury_source.consts import PLUGIN_NAME
from calibre_plugins.wolnelektury_source.consts import WOLNELEKTURY_ID

kovidgoyal · 06-23-2026, 08:53 PM

This should fix it: https://github.com/kovidgoyal/calibr...f07fb5eb0c692c

Lakis · 06-24-2026, 11:38 AM

Thanks everyone, I'll separate imports just for compatibility sake, but the fix seems nice either way

Lakis · Yesterday, 11:01 AM

As an info for anyone having similar problem: try running 'python plugins_mirror.py path_to_plugin_archive.zip' from setup folder in the official calibre repo here and debug from there. If everything is fine, it should display all required data fields from the plugin definition correctly scrapped from __init__.py

I tried it after another issue had appeared and it was the matter of adding type annotations to all variables and functions, including members of my Source class. With those in place plugin could not be parsed, removing them for the members solved the problem.

kovidgoyal · Today, 02:32 AM

@Lakis: If you give me an example of type annotations that cause issues, I will see if I can improve the parser to handle them as the parser was written before type annotations existed in python.

Lakis · Today, 09:03 AM

Sure, here is the version of my plugin's __init__ file in which this issue was present.

06-23-2026, 02:07 PM	#1
Lakis Junior Member Posts: 9 Karma: 58226 Join Date: Jun 2026 Device: Kindle Paperwhite 4	Plugin index - entry not included in calibre list One of the mods added my plugin to the index (post is here), but so far (it's over a week) it's not visible in the calibre plugins' list. I'm thinking, if it's something in my plugin's structure or something else. On my side I was thinking, if version and plugin name in side file (consts.py, then imported to __init__.py and used in Source class) are making any problems for the Plugin updater to read required data and it skips it or is it something else.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre help? IndexError: list index out of range	ideamutt	Editor	5	01-08-2025 02:26 PM
Getting Goodreads into Calibre using import list plugin	Rellwood	Library Management	3	12-12-2018 12:12 AM
Python Libraries included in Plugin?	JimmXinu	Development	5	06-15-2014 06:48 AM
Tablet only for manga, list of choices included	Tanyu22	Which one should I buy?	3	11-01-2011 04:41 PM

06-23-2026, 02:52 PM	#2
theducks Well trained by Cats Posts: 31,853 Karma: 64181416 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	I looked at the Index of plugins and see the entry (code) and did not spot why it is not being scraped to include in the Get Plugins list (also deal with updates). The name in the init is not what is used for the list.

06-23-2026, 04:43 PM	#3
Comfy.n want to learn what I want Posts: 2,301 Karma: 7990245 Join Date: Sep 2020 Device: Libra Colour	I found that splitting the imports makes the parser happy: from calibre_plugins.wolnelektury_source.consts import PLUGIN_VERSION from calibre_plugins.wolnelektury_source.consts import PLUGIN_NAME from calibre_plugins.wolnelektury_source.consts import WOLNELEKTURY_ID

06-23-2026, 08:53 PM	#4
kovidgoyal creator of calibre Posts: 46,356 Karma: 29630884 Join Date: Oct 2006 Location: Mumbai, India Device: Various	This should fix it: https://github.com/kovidgoyal/calibr...f07fb5eb0c692c

06-24-2026, 11:38 AM	#5
Lakis Junior Member Posts: 9 Karma: 58226 Join Date: Jun 2026 Device: Kindle Paperwhite 4	Thanks everyone, I'll separate imports just for compatibility sake, but the fix seems nice either way

Yesterday, 11:01 AM	#6
Lakis Junior Member Posts: 9 Karma: 58226 Join Date: Jun 2026 Device: Kindle Paperwhite 4	As an info for anyone having similar problem: try running 'python plugins_mirror.py path_to_plugin_archive.zip' from setup folder in the official calibre repo here and debug from there. If everything is fine, it should display all required data fields from the plugin definition correctly scrapped from __init__.py I tried it after another issue had appeared and it was the matter of adding type annotations to all variables and functions, including members of my Source class. With those in place plugin could not be parsed, removing them for the members solved the problem.

Today, 02:32 AM	#7
kovidgoyal creator of calibre Posts: 46,356 Karma: 29630884 Join Date: Oct 2006 Location: Mumbai, India Device: Various	@Lakis: If you give me an example of type annotations that cause issues, I will see if I can improve the parser to handle them as the parser was written before type annotations existed in python.

Today, 09:03 AM	#8
Lakis Junior Member Posts: 9 Karma: 58226 Join Date: Jun 2026 Device: Kindle Paperwhite 4	Sure, here is the version of my plugin's __init__ file in which this issue was present.