New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Pin w3lib version as requirement (or update library to be able to use newest w3lib versions) #417

Open

rennerocha opened this issue Jan 27, 2025 · 1 comment

rennerocha commented Jan 27, 2025

w3lib 2.3.0 removed to_native_str (https://github.com/scrapy/w3lib/releases/tag/v2.3.0) function. So we are unable to use the latest version of this library now:

  File "./.venv/lib/python3.10/site-packages/frontera/core/models.py", line 3, in <module>
    from w3lib.util import to_bytes, to_native_str
ImportError: cannot import name 'to_native_str' from 'w3lib.util' (./.venv/lib/python3.10/site-packages/w3lib/util.py)

The text was updated successfully, but these errors were encountered:

Gallaecio mentioned this issue

Release 0.9.0 #416

Closed

1 task

Member

Gallaecio commented Jan 29, 2025

@rennerocha Are you using only frontera, or scrapy-frontera as well? I’m looking for people to test the combination of scrapinghub/scrapy-frontera#14 and #416 on real code before merging and releasing, since the test coverage of https://github.com/scrapinghub/scrapy-frontera does not give me much confidence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment