-
Notifications
You must be signed in to change notification settings - Fork 10.6k
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
DeprecationWarning: Passing method to twisted.internet.ssl.CertificateOptions was deprecated #3288
Comments
How did you get these warning? |
I've recently also started getting these and a few other warnings but it turned out to be one of the spiders in the project was importing a certain library which tinkered with the |
Thanks @Unknowny |
@kmike I can reproduce the first warning (made visible by pytest):
We are indeed using Should we reopen this issue? |
I find this somewhat frustrating. I could not find any release notes for v16.7.0 talking about this deprecation, in fact there is no mention of "16.7.0" in https://github.com/twisted/twisted/blob/trunk/NEWS.rst and https://twistedmatrix.com/documents/current/api/twisted.web.client.HTTPClientFactory.html says nothing about it being deprecated. |
I believe this is the point before the last of the deprecation list of Twisted Core 17.1.0. It’s easy to miss because it does not mention the factory at all. You can see the 8960 ticket in their issue tracking system for additional information, although the actual pull request, twisted/twisted#643, may be more useful. |
So I've read the links above and I still don't understand if the problems mentioned there are applicable to Scrapy. Should we plan to replace this code with the modern one? |
That would be great, in my opinion, much cleaner than #4165. However, there’s a risk of introducing changes of behavior. And there’s the argument that HTTP 1.0 usage is dropping, so if such a change requires a lot of effort, it may not be worth it. |
But the "replacement code" is the HTTP1.1 downloader already, IMO. Edit: Sorry, I got this wrong, tests say the http10 handler does handle HTTPS just fine, even does TLS SNI, it seems. So that's a bogus argument from me. |
The second warning is still an issue. Offending line:
|
I got the same warning when running all the unit tests like:
|
Yes, the issue is still open. |
May you do a little modification to avoid these two warnings?
The text was updated successfully, but these errors were encountered: