Delete pyproject.toml in override-build in flask/django
Metadata
Current evaluation
Superseded in favor of canonical/craft-parts#747. The change to automatically delete pyproject.toml for flask and django extensions was deferred to a separate tracking issue to address dependency resolution conflicts.
Suggested action: —
No scores available.
Issue body
- [X] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
-----
File `pyproject.toml` is not necessary for django/flask extensions, as there is no need to create a Python package.
Besides, for some project like NetBox, the `pyproject.toml` breaks the build.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Superseded in favor of canonical/craft-parts#747. The change to automatically delete pyproject.toml for flask and django extensions was deferred to a separate tracking issue to address dependency resolution conflicts. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed and superseded by craft-parts#747. The PR proposed deleting pyproject.toml for flask/django extensions to prevent build failures. Maintainers clarified its dependency role, and the author redirected the fix to the referenced issue. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Superseded by craft-parts#747. The proposed pyproject.toml deletion for flask/django overrides was closed after discussion highlighted broader dependency management implications, leading to a more comprehensive solution in the referenced issue. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.