Repository navigation
Rename this repo and PyPI project to openedx-core #470
Description
- Rename the repo to
openedx-corefrom GH settings. - In one PR (build!: Rename the PyPI project to
openedx-core#471)- Update the README and a add a little note about the former name
- Create a sub-folder called
tmp-openedx-learning. This will be our backcompat "shell" project.- Add basic setup.py. Set the project name to
openedx-learning - Add a basic description which redirects the user to
openedx-core. - Set the version number one zero-versioned major version higher than the current release.
- Its package list should be empty (i.e., no source folders)
- Its install_requires should contain
openedx-core, ensureing that installing openedx-learning will now forward you to the new name.
- Add basic setup.py. Set the project name to
- Edit pypi-publish so that it also runs this new setup.py. Add a note that it's temporary and link to this ticket.
- Back in the real setup.py, rename the project to
openedx-core. - Double-bump the version number (so that it is the version of tmp-openedx-learning, plus 0.1.0), add a changelog entry.
- Merge. This should trigger the release workflow for both openedx-learning (now a shell project) and openedx-core (the real project)
- delete the tmp-openedx-learning directory and the extra pypi-publish workflow setps.
- In openedx-platform's pip reqs, remove openedx-learning and add openedx-core. Run
make compile-requirements. Grep for any openedx-learning refernces and update to openedx-core. Commit and merge. - Grep the openedx GH org for openedx-learning and update it to openedx-core (or openedx_content, the new name for the authoring package) as it's reasonable and helpful to.
Metadata
Metadata
Assignees
Labels
No labels
Activity
kdmccormick commentedon Jan 30, 2026
I can take this one on, though I think we'll want to wait until after #468 so there isn't so much in flux at the same time.
openedx_contentis a top-level package #468kdmccormick commentedon Jan 30, 2026
fyi @feanil , since you'd also mentioned a need to rename PyPI projects -- here is my stab at how we're going to rename openedx-learning to openedx-core. I'll let you know how it works out.
kdmccormick commentedon Jan 30, 2026
Draft PR: #471
feanil commentedon Jan 30, 2026
Looks like PyPI doesn't support re-naming so we'll just have to ship to the new name at the new version when we're ready for that, and archive the old project. So we'll need to make sure we've got good docs during the transition (ie. a last publish before we move pointing to the new package location.)
kdmccormick commentedon Jan 30, 2026
Yup, the mechanics of that is what I've laid out here
build!: Rename the PyPI project to `openedx-core`
build!: Rename the PyPI project to `openedx-core`
build!: Rename the PyPI project to `openedx-core`
build!: Rename the PyPI project to `openedx-core`
build!: Rename the PyPI project to `openedx-core`
build: Release 0.34.1 and delete tmp-openedx-learning
build!: Switch to openedx-core (renamed from openedx-learning)
build!: Switch to openedx-core (renamed from openedx-learning)
build!: Switch to openedx-core (renamed from openedx-learning)
build!: Switch to openedx-core (renamed from openedx-learning)
build!: Switch to openedx-core (renamed from openedx-learning) (#38011)
fix: Migrate `LanguagesTaxnomy._taxonomy_class` to reflect refactoring
fix: Migrate `LanguagesTaxnomy._taxonomy_class` to reflect refactoring
fix: Migrate `LanguagesTaxnomy._taxonomy_class` to reflect refactoring (
docs: Learning Core -> openedx_content
docs: Learning Core -> openedx_content (#165)
docs: Learning Core -> openedx_content (#165)