Skip to content
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.

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

Explicitly mention PythonItemExporter output changes in 2.11 (#6060) #6062

Conversation

AlexMuresan
Copy link

@AlexMuresan AlexMuresan commented Sep 23, 2023

resolves #6060

@@ -40,6 +40,9 @@ Backward-incompatible changes
UTF-32). If you need to deal with JSON documents in an invalid encoding,
use ``json.loads(response.text)`` instead. (:issue:`6016`)

- :class:`~scrapy.exporters.PythonItemExporter` used the binary output by defauilt
but it no longer does (:issue:`6006`, :issue:`6007`)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
but it no longer does (:issue:`6006`, :issue:`6007`)
but it no longer does. (:issue:`6006`, :issue:`6007`)

@@ -40,6 +40,9 @@ Backward-incompatible changes
UTF-32). If you need to deal with JSON documents in an invalid encoding,
use ``json.loads(response.text)`` instead. (:issue:`6016`)

- :class:`~scrapy.exporters.PythonItemExporter` used the binary output by defauilt
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- :class:`~scrapy.exporters.PythonItemExporter` used the binary output by defauilt
- :class:`~scrapy.exporters.PythonItemExporter` used the binary output by default

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Explicitly mention PythonItemExporter output changes in 2.11
2 participants