-
Notifications
You must be signed in to change notification settings - Fork 219
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
New release with support for django 3.2 #268
Comments
@kennethlove @chrisjones-brack3t Could you please look into this PR? We are the Open edX team would highly appreciate. |
Hi, sorry, yes, we've been meaning to go over several PRs lately but just
have not had time yet.
…On Mon, Oct 18, 2021 at 10:51 AM Natalia Berdnikov ***@***.***> wrote:
@kennethlove <https://github.com/kennethlove> @chrisjones-brack3t
<https://github.com/chrisjones-brack3t> Could you please look into this
PR? We are the Open edX team would highly appreciate.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#268 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAC5BEMMIBZSJ5GE4ZW6P3UHRNB3ANCNFSM5EIGT2PA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Should have a release out today. 👍🏻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @kennethlove @chrisjones-brack3t!
The edX project is looking forward to using django-braces with Django 3.2. Here is the associated Github issue edx/upgrades#23
I noticed that PR #265 added support for Django 3.2.
Are there any chances this PR could get reviewed and merged so a new version can be released anytime soon? I would be happy to help in case there are any blockers with this.
Thank you in advance!
The text was updated successfully, but these errors were encountered: