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
JSONRequest naming issue #3929
Comments
Maybe we should consider renaming the other 3 instead to comply with PEP8. |
@Gallaecio Totally agree with you. We should decide what to do:
If we decide to change it:
I have just opened an issue regarding PEP8: #3944. Maybe it should be addressed before deciding the second question. |
|
Looking over I have seen that this issue affects at least the following classes:
(Apart of a lot of test classes). |
|
Tbh, I'd leave everything as-is, probably including JSONRequest; it is not super consistent, but my feeling is that changing it doesn't worth the development efforts required to upgrade (change in settings, imports, etc.) |
I'm agree with you, there are too much classes to deprecate... If all of you are agree feel free to close this issue. |
We may still change JSONRequest though, to at least match XmlRpcRequest - that's what you propsed in #3930 . |
As all the classes in Scrapy starting with "JSON" ( If you all want to proceed I can re-open the original PR and adding the code to deprecate that class. |
Added new PR: #3982 (I deleted the old branch from my repo and couldn't open the old PR). |
I close this issue as PR has been already merged. Thank you all for your feedback! :) |
A few months ago
JSONRequest
was added to Scrapy (#3505) and released with the new Scrapy version 1.7.However, I realized that the name is not in accordance with the rest of the classes:
HtmlResponse
,XmlResponse
,XmlRpcRequest
.It should be named:
JsonRequest
.I know it isn't backward-compatible, but as it's a really recent addition and Scrapy 2.0 is on the way it could be fixed.
The text was updated successfully, but these errors were encountered: