-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
AttributeError: 'NoneType' object has no attribute 'get_extra_info' #3335
Comments
GitMate.io thinks possibly related issues are #2231 (AttributeError: 'NoneType' object has no attribute 'errno'), #1903 (AttributeError: 'NoneType' object has no attribute 'set_exception' ), #340 (AttributeError: 'NoneType' object has no attribute 'handle_expect_header'), #2840 (AttributeError: module 'asyncio' has no attribute 'current_task'), and #2546 (AttributeError: 'NoneType' object has no attribute 'feed_appdata'). |
Sorry. I dont follow what introspection are you talking about |
@asvetlov updated to hopefully be more clear. Basically, calling |
Please check aiohttp master. |
@asvetlov is this not supposed to work with Pyhon 3.5.5? I tested it and got the same error as before:
|
Read somewhere that the fix was not backported..so it requires 3.6.5 |
@tmendo you are talking about the completely different bug. Anyway, regarding your question: no, the fix wan not backported because Python 3.5 is in security maintenance mode now. It means that only the Release Manager (Larry Hastings in this case) can choose what bugfixes to backport, and he should have a Very Serious Reason to do it. Basically, 3.5 is closed for bugfixes except for security vulnerabilities. I personally was the reviewer and committer for this particular bug; the best I can advise is migrating to 3.6 (or even 3.7, 3.7.1 will be published in a week). |
Close as fixed, will be published as a part of aiohttp 3.5 release |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs. |
Long story short
When request object is closed,
request.transport
is set toNone
which causes errors if you want to do any introspection on the request afterwards(like simply doingrequest.url
)Expected behaviour
To be able to call
request.url
object after it is closed.Actual behaviour
request.url
gives:Steps to reproduce
Your environment
extra
Similar to #816
workaround
If you call
request.url
before the request is closed, it will be cached and you will not get this error.The text was updated successfully, but these errors were encountered: