edx-platform

Files

Julia Eskew a9b534e10b fix: Use a "through" model for the ManyToManyField fields in CourseSection

and CourseSectionSequence to ensure that cascading deletes will occur to delete
the relation upon deletion of a foreign-keyed object.

This commit is phase 1 of 3 in order to ensure a smooth deploy. The phases:
1) Add separate through models for user partition groups, add fields to point to the
   separate models, and start writing to those fields as well.
2) After all models have been re-generated, switch code over to use separate through
   model fields backed by the separate through models.
3) After phase 2 is deployed smoothly, remove the original ManyToManyField fields
   and rename the new fields to have the same name as the old fields.

2021-06-24 12:17:54 -04:00

core

fix: Use a "through" model for the ManyToManyField fields in CourseSection

2021-06-24 12:17:54 -04:00

features

feat: AA-797 switch course home flag to opt out by replacing it with a course home use legacy frontend flag

2021-06-16 10:04:49 -04:00

testing

refactor: Ran pyupgrade on openedx/{testing, tests}

2021-04-08 14:49:40 +05:00

tests

feat: initialize agreements app

2021-05-10 17:55:36 -04:00

__init__.py

style: django-not-configured is not a sensible lint-amnesty value (#26862 )

2021-03-05 08:11:58 -05:00

README.rst

…

README.rst

Open edX
--------

This is the root package for Open edX. The intent is that all importable code
from Open edX will eventually live here, including the code in the lms, cms,
and common directories.

If you're adding a new Django app, place it in core/djangoapps. If you're adding
utilities that require Django, place them in core/djangolib.  If you're adding
code that defines no Django models or views of its own but is widely useful, put it
in core/lib.

Note: All new code should be created in this package, and the legacy code will
be moved here gradually. For now the code is not structured like this, and hence
legacy code will continue to live in a number of different packages.