Beta testers needed

[PandathePanda]

Originally Posted by kovidgoyal

soupsieve is installed -- probably fanficfare is using a custom beautifulsoup it should be updated to use the calibre beautifulsoup

You can test it with

calibre-debug -c "import soupsieve; print(soupsieve)"


The KDE error has nothing to do with the beta and can be ignored.

I get this:

./calibre-debug -c "import soupsieve; print(soupsieve)"
Traceback (most recent call last):
File "site.py", line 77, in main
File "site-packages/calibre/debug.py", line 277, in main
File "<string>", line 1, in <module>
File "site-packages/soupsieve/__init__.py", line 30, in <module>
File "site-packages/soupsieve/css_parser.py", line 4, in <module>
File "site-packages/soupsieve/util.py", line 25, in <modul

[eschwartz]

I've tested fanficfare and it seemed to work :/ but it does contain a bundled bs4 4.6.1 and no soupsieve. I'm not clear on how it actually imports it, though. It just uses "from bs4 import ..." and includes bs4/* in the root of the zip.

[JimmXinu]

I submit that's possibly the opposite problem, since FFF includes BS4.6.1 and BeautifulSoup doesn't use SoupSieve in that version:

As of version 4.7.0, Beautiful Soup supports most CSS4 selectors via the SoupSieve project. If you installed Beautiful Soup through pip, SoupSieve was installed at the same time, so you don’t have to do anything extra.

BeautifulSoup has a .select() method which uses SoupSieve to run a CSS selector against a parsed document and return all the matching elements. Tag has a similar method which runs a CSS selector against the contents of a single tag.

(Earlier versions of Beautiful Soup also have the .select() method, but only the most commonly-used CSS selectors are supported.)

So I suspect that what PandathePanda is seeing is Calibre's included BS4.7 being used in at least part of the FFF code and not finding SoupSieve for whatever reason. Because the BS4.6.1 included in FFF shouldn't need it.

But that's speaking theoretically, I haven't tried the beta version yet myself.

[eschwartz]

@JimmXinu, any plans for dropping the libraries bundled in calibre and updating the minimum supported version for the plugin?

[eschwartz]

@PandathePanda, your error message is cut off, but it looks like your calibre installation is itself somehow broken.

[kovidgoyal]

That looks like one of soupsieve's dependencies is missing, i will investigate in a bit.

[PandathePanda]

Originally Posted by eschwartz

@PandathePanda, your error message is cut off, but it looks like your calibre installation is itself somehow broken.

not sure why that happened. Here is it in full:

Traceback (most recent call last):
File "site.py", line 77, in main
File "site-packages/calibre/debug.py", line 277, in main
File "<string>", line 1, in <module>
File "site-packages/soupsieve/__init__.py", line 30, in <module>
File "site-packages/soupsieve/css_parser.py", line 4, in <module>
File "site-packages/soupsieve/util.py", line 25, in <module>
ImportError: No module named backports.functools_lru_cache

[kovidgoyal]

This should take care of the soupsieve import failure:
https://github.com/kovidgoyal/calibr...f851956f4c12c7

[kovidgoyal]

released 3.40.5 with the soupsieve fix.

[Terisa de morgan]

At this moment I'm using this beta with the following plugins, and no problem:

• Overdrive (Fixed in the new release)
• ImportList (Fixed in the beta)
• Kobo Utilities
• Goodreads Sync
• Metadata for Goodreads (modified for returning the right id )
• Extract ISBN
• Get File Name
• Annotations
• Count Pages (the initial problem should be a glitch)
• View Manager
• Modify ePub
• Search Internet

No difference with standard calibre

[phossler]

Is there a list of changes / improvements in or planned for ver 3?

[kovidgoyal]

No not really. The major change in calibre 4 is going to be that various bits of calibre are moving from Qt WebKit to Qt WebEngine (because the former has been deprecated). In particuarthe viewer has been completely re-written, it now shares a code base witht he in-browser viewer, which means support for annotations can be added to both relatively easily.

[Terisa de morgan]

It looks like the "Count Pages" error is not random, and it's related to the book. When I try to view one of those books, the viewer fails too with this log:

Spoiler:

calibre, version 3.40.5
ERROR: No se pudo abrir el libro electrónico: Fallo al leer el libro, D:\Biblioteca Kindle\Adquisiciones\Edith Maxwell\Delivering the Truth (14494)\Delivering the Truth - Edith Maxwell.epub pulse en «Mostrar detalles» para más información

Traceback (most recent call last):
File "site-packages\calibre\utils\ipc\simple_worker.py", line 291, in main
File "site-packages\calibre\ebooks\oeb\iterator\book.py", line 65, in extract_book
File "site-packages\calibre\customize\conversion.py", line 245, in __call__
File "site-packages\calibre\ebooks\conversion\plugins\epub_in put.py", line 309, in convert
File "site-packages\calibre\ebooks\conversion\plugins\epub_in put.py", line 407, in convert_epub3_nav
File "site-packages\calibre\ebooks\metadata\opf2.py", line 717, in create_manifest_item
OverflowError: Python int too large to convert to C long

Adobe can open them without problem.

[kovidgoyal]

This should take care of it:

https://github.com/kovidgoyal/calibr...77e3d1f9f4771e

[Terisa de morgan]

Thank you, I'll test it when there is a new beta.