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.

Sign up for GitHub

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

Jump to bottom

Multithreaded use of the library #5

Closed
shenberg opened this issue Jul 13, 2012 · 4 comments
Closed

Multithreaded use of the library #5

shenberg opened this issue Jul 13, 2012 · 4 comments

Comments

@shenberg
Copy link

balanced.configure() must be called for every thread since the configuration inherits from threading.Local. This is not mentioned anywhere in the documentation, and causes issues in development - when using the interpreter or test scripts everything will work, but on an actual multi-threaded web server, things will start breaking for what can seem to be no reason at all.
@mahmoudimus
Copy link
Contributor

Yes, this is a huge design mistake on my part. I will fix ASAP.

@streed
Copy link
Contributor

streed commented Sep 29, 2012

Has there been an update on this issue? I have a method of getting around it via injection that works, but it just feels messy.

Nonetheless the only gripe so far.

@streed streed mentioned this issue Sep 30, 2012
Merged
@mahmoudimus
Copy link
Contributor

Done.

@chadwhitacre
Copy link
Contributor

!m @mahmoudimus

chadwhitacre added a commit to gratipay/gratipay.com that referenced this issue Apr 2, 2014
@chadwhitacre
Take out configure_payments hack
a3100a9 
With the upgrade to the balanced library in #2036 we no longer need this
workaround for balanced/balanced-python#5.
Removing at this point because I'm ripping out all of our direct
os.environ usage and this applies.
@chadwhitacre chadwhitacre mentioned this issue Apr 2, 2014
Merged
chadwhitacre added a commit to gratipay/gratipay.com that referenced this issue Apr 3, 2014
@chadwhitacre
Take out configure_payments hack
bcf777b 
With the upgrade to the balanced library in #2036 we no longer need this
workaround for balanced/balanced-python#5.
Removing at this point because I'm ripping out all of our direct
os.environ usage and this applies.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mahmoudimus @chadwhitacre @shenberg @streed