Opened 99 minutes ago
Closed 10 minutes ago
#36922 closed Bug (needsinfo)
Commit 787cc96e is reachable from main but not 6.0.2
| Reported by: | Julien Palard | Owned by: | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 6.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Julien Palard, Jacob Walls | Triage Stage: | Unreviewed |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I tried to run django-oscar tests using django 6 and spotted an AttributeError: 'tuple' object has no attribute 'extend' that has been fixed by 787cc96ef6197d73c7d4ad96f25500910c399603, which does not exists in the stable/6.0.x branch.
Change History (2)
comment:1 by , 82 minutes ago
comment:2 by , 10 minutes ago
| Cc: | added |
|---|---|
| Resolution: | → needsinfo |
| Status: | new → closed |
Hello Julien, thank you for your ticket. The commit you reference was merged into main after the 6.0 feature freeze (this is when the stable/6.0.x branch is cut), that's why the commit is not there. Now, whether this commit should have been backported, that's another question. In the PR, Jacob explicitly said:
Not certain whether to suggest a 6.0 backport. Nothing is broken per se, it's just two examples falling outside the doc'd pattern we updated to.
Can you please provide more details about your use case and how your project is affected? Please reopen the ticket when doing so. Thank you!
This is mentionned in Django 6.0 release notes :)
https://docs.djangoproject.com/en/6.0/releases/6.0/#custom-orm-expressions-should-return-params-as-a-tuple