You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are looking to use this package to implement twilio integration in our django 3.2 project. Unfortunately, it seems that this package only supports from 4.0 and up. Is it possible to extend support to the latest 3.x version? Are there any django 4.x specific features that this package is relying on?
The text was updated successfully, but these errors were encountered:
I think I see your point, given that 3.2 has security support until April 2024. The mainstream support has long ended, and that's probably what the impetus for the change was.
Can you share any of the features, bugs, or security fixes that have been applied (and are relevant against django 3.2+) to this codebase that are not available since the removal of 3.2 support, but that you'd prefer, or require/need?
The ask is helpful in case we can just make a small set of changes on a back-port branch at the appropriate point in the git tree. Potentially we could just re-enable 3.2 support, but nonetheless, if you could, that would [I think] be helpful.
Thank you. we ended up using two classes from this library, just copying them over. Seems to be working for our use case, though we obviously can't pull in updates.
Hi,
We are looking to use this package to implement twilio integration in our django 3.2 project. Unfortunately, it seems that this package only supports from 4.0 and up. Is it possible to extend support to the latest 3.x version? Are there any django 4.x specific features that this package is relying on?
The text was updated successfully, but these errors were encountered: