Codex suggesting outdated Python syntax - how to guide it toward modern patterns?

[BittuChan]

Hey all,
I'm using Codex via the API for Python code generation, but I'm noticing it often suggests older patterns like os.path methods instead of pathlib or requests without context managers.

For example, when I prompt "read a JSON file," it generates:

import json

with open('data.json', 'r') as f:
    data = json.load(f)

Which works fine, but I'd prefer it to use pathlib.Path for file operations. Is there a way to bias Codex toward modern Python 3.10+ idioms without overly verbose prompts? I've tried adding "using pathlib" to my prompts, but results are inconsistent.
Any tips?

[Shiven0504]

hey @BittuChan, You can fix Codex pretty effectively by including a few lines of example code in your prompt as context. Think of it like "few-shot" prompting. You can try something like:

# Modern Python using pathlib and type hints
from pathlib import Path
import json

def read_config(path: Path) -> dict:
    return json.loads(path.read_text())

# Now write a function to read JSON data from a file:

Codex will pick up on the style and continue in that pattern. You can also add a comment at the top like # Python 3.10+ with modern idioms to set expectations.

[Shiven0504]

Another trick: if you're using it through the Playground or API, keep a "style template" as a system message or prefix that defines your coding standards. Codex is pretty good at following established patterns once you show it what you want.

[BittuChan]

Hii @Shiven0504 thanks for the quick suggestion! I created a small template file with pathlib examples and included the first few lines in my prompts now.

[BittuChan]

The few-shot approach worked way better than I expected. Its even suggesting Path.read_text() and Path.write_text() without me asking. Big improvement.

Thanks for the tip! Solved.