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

Update request future (#1) #2

Closed
wants to merge 4 commits into from
Closed

Update request future (#1) #2

wants to merge 4 commits into from

Conversation

@wangsha
Copy link

@wangsha wangsha commented Dec 4, 2018

latest request_future package is deprecating background_callback method in favour of hooks.
the warning message itself is generating a lot of logs.
update the method solves the problem.

screenshot 2018-12-04 at 11 27 37 am

Warning messages

screenshot 2018-12-04 at 2 10 01 pm

Issue fixed
* Update requirements.txt

* Update handlers.py

deprecate 'background_callback', use hooks
@@ -9,10 +9,12 @@
session = FuturesSession()


def bg_cb(sess, resp):

def bg_cb(resp, *args, **kwargs):

This comment has been minimized.

@lancondrej

lancondrej Jan 2, 2019

I prefer to rename it to response_hook because it is not background callback anymore.

This comment has been minimized.

@wangsha

wangsha Jan 2, 2019
Author

updated

@@ -2,4 +2,4 @@ coverage==3.7.1
flake8==2.1.0
mock==1.0.1
nose==1.3.0
requests-futures==0.9.4
requests-futures>=0.9.9

This comment has been minimized.

@lancondrej

lancondrej Jan 2, 2019

Please change this dependency also in setup.py

This comment has been minimized.

@wangsha

wangsha Jan 2, 2019
Author

updated

This comment has been minimized.

@jerson00

jerson00 Nov 12, 2019

waiting for this merge, any update?

wangsha added 3 commits Jan 2, 2019
update requirements
rename background callback (bg_cp) to `response_hook`
* Update requirements.txt

* Update handlers.py

deprecate 'background_callback', use hooks

* update setup.py package requirement
rename background callback to response_callback
@cmawer
Copy link

@cmawer cmawer commented Mar 18, 2019

It would be great if this could be merged in as this deprecation warning is producing more logs than my application itself.

@dnshio
Copy link

@dnshio dnshio commented Jun 13, 2019

+1 it is outright broken right now because of this issue. I can't even install the package anymore

@maciejstromich
Copy link

@maciejstromich maciejstromich commented Jun 25, 2019

+1 it is outright broken right now because of this issue. I can't even install the package anymore

#6

@jerson00
Copy link

@jerson00 jerson00 commented Nov 5, 2019

Any update about this???

@MichalChomo
Copy link

@MichalChomo MichalChomo commented Dec 3, 2019

These changes are included in #7. Closing this.

@MichalChomo MichalChomo closed this Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

7 participants
You can’t perform that action at this time.