Start installing codejail requirements from base.txt instead of py38.txt

[timmc-edx]

The structure of the edxapp-sandbox-requirements has changed and we need to switch in order to keep getting updates: openedx/edx-platform#34509

First step: Determine priority, may be able to lower it.

[kdmccormick]

Nice, you caught this before I got around to bugging you about it :) Just a heads up, as I tried to explain here, we plan to keep requirements/edx/base.txt and requirements/edx-sandbox/base.txt synced in terms of constraints and language version. So, once Py3.8 support is dropped from edx-platform, it will be simultaneously be dropped for edx-sandbox. That might be exactly what you folks want, or it might not be, I'm not sure--just want to make sure you folks have all the information you need as you decide between quince.txt redwood.txt and base.txt.

[jristau1984]

Putting down a due date of "something like the Sumac release", so that we dont lose this. The thought is that this can be added to a "pipeline" related epic in H2 2024.

[robrap]

Noting that it is entirely up to 2U when we want to get off an unsupported version of Python. It would be good for us to clean-up the unused file once we are done with it, but Axim does not plan on deleting this file. In other words, we don't have an external deadline for this work.

[robrap]

Additional questions:

1. Would it makes sense to move to Python 3.12 (rather than 3.11) to minimize the number of upgrades?
2. Would it make sense to bump Ubuntu versions to minimize upgrades? See Test edx-platform on Ubuntu 22.04 openedx/edx-platform#35314

[robrap]

Note: Ubuntu 20.04 standard support runs out April 2025, and this upgrade work may need to be ticketed separately with SRE. I simply wanted to note that we need to take some action somewhere.

[robrap]

[inform] We missed the due date. Do we want to schedule this work?

[robrap]

FYI: @jristau1984

[jristau1984]

@robrap I believe that Arbi-BOM started the upgrade the sandbox environment to Python 3.11 as a pre-requisite for several other testing efforts where sandboxes were needed. This is the issue related to that effort: #850.

It looks like there is a need to complete that work, which I will follow up with ARbi-Bom about in our next touchpoint.

[robrap]

@timmc-edx: Can you confirm if this is complete? Thank you.

[timmc-edx]

No, our codejail is still running in Python 3.8.10. (This is distinct from 2U's sandboxes; "sandbox" in the meaning of this ticket actually refers to codejail.)

EDIT: Here's a quick way to check the codejail environment if you can add a problem to a course:

<problem>
  <customresponse>
    <script type="loncapa/python">

import sys
out = f"Python version: {sys.version}"

    </script>
    <p>Output:</p>
    <pre>$out</pre>
  </customresponse>
</problem>

[robrap]

We're considering whether it would be better to do this before or after containerization.

[kdmccormick]

Separate from 2U's edx-sandbox 3.8->3.11 upgrade, the cleanup that we're hoping to do from the openedx side is just to delete py38.txt, which is just a simple pointer to quince.txt. To avoid being broken by that cleanup, I recommend just updating your edx-sandbox deployment to point at quince.txt instead of py38.txt. You could then schedule the 3.8->3.11 edx-sandbox upgrade at your own pace with no openedx-based pressure.

[robrap]

@kdmccormick: Do you know why quince.txt is crossed out in your earlier comment? See #630 (comment)

[kdmccormick]

I do not-- I must have been confused. quince.txt is indeed what you want if you have been using py38.txt up until this point.

[robrap]

PR for pointing to more permanent requirements file:

• fix: switch py38.txt to releases/quince.txt configuration#141

[robrap]

• When we land the PR I posted, we should be able to do the minor clean-up of removing the py38.txt file.
• Separately, Python 3.8 has gone out of support, so we'll still want to complete the upgrade.