[refactor] Rewrite the content app in Django
Open
Nobody has claimed this yet.
Task
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Django 4 has async views and can act as a wsgi app. The lack of this has been the main reason write the content app in the aiohttp framework.
Reasons:
- Having the whole codebase use one framework instead of two is good for maintainability and a better understanding easier onboarding.
- Using the Django ORM within the other framework lead to nasty bugs (maybe or maybe not fully resolved).
We should keep an eye on performance.
https://discourse.pulpproject.org/t/refactor-of-the-content-app-in-django/848
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the content app implementation and the linked Discourse discussion about refactoring it to Django. Compare the current aiohttp and Django integration points, keeping performance in view. Done means the content app runs on Django without the existing two-framework arrangement and its behavior remains covered by the project’s checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100