Jerome Leclanche

Yes, release 2.10 will feature both options. Making changes now to it.

I don't see why it shouldn't be in the db if encrypted. There is an actual reason we're storing it in there: This is the only way to enable dynamic,...

Closing to keep discussion in #2055

This is likely a variation of the deadlocks that sometimes happen on webhook endpoints. I will study your trace a little closer because you mention it's only happening with this...

Hi @sergiogomesan8 sorry for the delay. What is the user model you're using? the djstripe_customer table points back to it, so it could be triggering a deadlock this way. But...

I don't really know what can be done here tbh. Like you said, stripe-python is not async, and django's async code is just super repeated, so I don't think we're...

Great to hear stripe-python now supports async. Let's get 3.0 out of the door first, but I'm open to a decent design for it.

Nope. using cwd overrides.

@BYK this is needed for example if we want to avoid using `cwd` directives when deploying using eg. ansible, or anything else that is cwd-agnostic.

Thanks for the report. How are you triggering this in the first place?