Upgrade Docker setup to Python 3.13

[Thejas1906]

Description

This PR updates the Docker environment for GPT Engineer to use Python 3.13, enabling compatibility with the latest Python version.

Changes include

• Updated base images in the Dockerfile from python:3.11-slim → python:3.13-slim.
• Adjusted Python library paths to match Python 3.13.
• Ensured all dependencies (openai>=1.0.0, backoff) remain installed and functional.
• Maintained existing multi-stage Docker setup and entrypoint configuration.

Motivation

• Support Python 3.13 for users who run GPT Engineer on the latest Python versions.
• Showcase GPT Engineer on YouTube using Python 3.13.

Impact

• No functional changes to the application.
• Existing projects and workflow remain compatible.

---

Important

Upgrade Docker setup to Python 3.13, updating base images, paths, and error handling.

• Docker Setup:
  • Update Dockerfile to use python:3.13-slim for both builder and final stages.
  • Adjust Python library paths to /usr/local/lib/python3.13/site-packages.
  • Ensure dependencies openai>=1.0.0 and backoff are installed.
• docker-compose:
  • Update docker-compose.yml to version 3.9.
• Entrypoint Script:
  • Add set -e in entrypoint.sh for immediate exit on errors.
  • Adjust file permissions handling in entrypoint.sh.

^{This description was created by for fc57ee1. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to fc57ee1 in 1 minute and 32 seconds. Click for details.

• Reviewed 103 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. docker-compose.yml:1

• Draft comment:
  Good practice: specifying Compose file version (3.9) clarifies compatibility. Ensure the API key is provided via .env or explicit environment vars as needed.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. docker/Dockerfile:19

• Draft comment:
  Wrap the package specifier 'openai>=1.0.0' in quotes (e.g. "openai>=1.0.0") to prevent shell redirection issues, and consider pinning exact versions for reproducibility.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 30% vs. threshold = 50% While version pinning is generally good practice, this seems more like a style preference than a critical issue. The shell redirection issue with > characters is technically valid, but in practice pip handles this correctly in most cases. There's no strong evidence that this has caused or will cause actual problems. The comment raises valid points about Docker best practices, and unquoted > characters could theoretically cause issues in some shell environments. However, this is more of a style suggestion than a critical fix, and pip generally handles unquoted version specifiers without issues in Docker contexts. Delete the comment as it's more of a style preference than a critical issue, and there's no strong evidence that the current approach is problematic.

3. docker/entrypoint.sh:9

• Draft comment:
  Consider using 'exec' (e.g. exec gpt-engineer "$project_dir" "$@") so signals are properly forwarded to the application.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_cmPlqgGMphCXSwLL

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}