Add support for django 4.2 - #1
Conversation
|
@pomegranited please review this PR. |
|
@bradenmacdonald can you please review this PR or ask some one from your team to make new one ? |
|
Hey @symbolist, is this plugin still used/needed on edx.org? |
|
@bradenmacdonald Nope. We are using our in process runtime now. Where exactly is this being referenced from? I think all LabXchange specific code should have been removed in: |
|
Thanks @symbolist. As I thought, just wanted to confirm. @awais786 I'm going to archive this repo - it shouldn't be used. If it's still installed on edx.org, please uninstall it and remove any associated database tables. Or do you need me to publish a "drop tables" migration first? |
|
@bradenmacdonald Its coming from configuration repo.
I'll talk to Jeremy and then inform you. Thanks |
|
@awais786 Thanks! The package above it can also be removed: |
|
@bradenmacdonald and @symbolist Looking at our mysql usage, it seems like we still have the lx_pathway table with data in it on prod. Making a quick drop tables migration would be great TYSM. After that is merged we can move to remove the plugin from configuration Evidence of data in table:
Hooray for getting rid of unused things! |
@bradenmacdonald kindly make a pr for |
|
@connorhaugh Sure. @awais786 The LabXchange team will take care of this. Will get back. |
|
We have assigned this internally. Should be ready next week. |
|
Thanks @symbolist |
|
@symbolist Sorry we missed that you mentioned someone from LabXchange team will take care of this. If they haven't yet done so, I have a PR for this: labxchange#17. CC @bradenmacdonald @awais786 |
|
@pkulkark We were going to get to it this week so looks like you beat us to it. Thanks! 🙂 |
|
@symbolist or @awais786 would one of you[r teams] mind reviewing the PR? |
|
@pkulkark PR seems fine. |
Hi,
This PR
Thanks,