Changes between Version 2 and Version 3 of SummerOfCode2026


Ignore:
Timestamp:
Feb 2, 2026, 3:51:33 AM (38 hours ago)
Author:
Bhuvnesh
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SummerOfCode2026

    v2 v3  
    152152Github reference: https://github.com/django/new-features/issues/23
    153153
     154
     155== Add ergonomic control over behaviour of missing variables in templates ==
     156
     157|| Difficulty || Medium
     158|| Size ||   350hr
     159|| Mentors || Lily(need confirmation)
     160|| Key Skills || python, django, template internals
     161
     162Templates silently convert missing variables to an empty string. This behaviour is useful in many situations:
     163
     164Pages still render instead of returning a 500 error when a minor programming error is made.
     165Template authors can deliberately design a section to be omitted when variables are not in the context.
     166However, this implicit behaviour is inconvenient for people who want to get an error during development when a variable that should always be present is omitted by mistake. By adding explicit syntax for required and optional variables, we give developers and teams extra control to opt-in to the desired behaviour where appropriate.
     167
     168Github reference: https://github.com/django/new-features/issues/5
     169
     170== Switch to Playwright tests for integration testing ==
     171
     172|| Difficulty || Medium
     173|| Size ||   175 hr
     174|| Mentors || TBD
     175|| Key Skills || python, django, playwright, CI/CD, testing
     176
     177This project aims to modernize Django’s integration testing by introducing Playwright as an alternative to Selenium. The work includes integrating Playwright with Django’s test framework, migrating existing browser-based tests, and ensuring compatibility with Django’s CI infrastructure. The goal is to improve test reliability, performance, and developer experience for Django core contributors.
     178
     179Full reference: https://github.com/django/new-features/issues/13
     180
     181== Add support for generate_series in postgres ==
     182
     183|| Difficulty || Hard
     184|| Size ||   350hr
     185|| Mentors || TBD
     186|| Key Skills || django, python, postgres, ORM
     187
     188This project aims to extend Django’s ORM with native support for PostgreSQL’s `generate_series` function. Currently developers must use raw SQL to access this powerful function. The work involves designing ORM expressions or query APIs to integrate `generate_series` in a way that feels natural within Django’s ORM, writing tests, and ensuring compatibility with Django’s PostgreSQL contrib utilities.
     189
     190References:
     1911. https://github.com/django/new-features/issues/25
     1922. https://forum.djangoproject.com/t/proposal-add-generate-series-support-to-contrib-postgres/21947
     193
    154194== [PLACEHOLDER] Project name ==
    155195
Back to Top