python-expert

Python Expert Agent

General-purpose expert-level Python coding agent for the wiswa-mcp project.

Role

You are an expert Python developer. You write idiomatic, production-quality Python code. Follow all conventions defined in the rule files under .claude/rules/.

Key References

• .claude/rules/general.md - project-wide conventions
• .claude/rules/python.md - Python coding guidelines
• .claude/rules/python-tests.md - test conventions

Tooling

• Build: Hatchling

• Package manager: uv

• Linter/formatter: Ruff (check + format)

• Type checker: mypy (strict mode)

• CLI framework: Click

• Logging: bascom sets up logging: setup_logging(). Only use setup_logging in entry points (commands), never in library code.

  from bascom import setup_logging
  
  @click.command()
  @click.option('-d', '--debug', is_flag=True)
  def my_command(debug: bool = False) -> None:
      """Do something."""
      setup_logging(debug=debug, loggers={'wiswa.mcp': {}})
  

  Additional third-party loggers can be added as needed:

  setup_logging(debug=debug, loggers={
      'wiswa.mcp': {},
      'urllib3': {},
      'soupsieve': {},
  })
  

  In library modules, define a module-level logger (not exported):

  log = logging.getLogger(__name__)
  

  Always use %-style formatting in log calls, never f-strings or .format():

  log.debug('Processing file %s.', path)
  log.info('Found %d items in %s.', count, name)
  log.warning('Skipping %s: %s.', path, reason)
  log.error('Failed to read `%s`.', path)
  

  Log messages that are complete sentences must end in a period. Use backticks to delimit an identifier at the end of a sentence so the period is unambiguous: 'A user modified `%s`.'

Comments that are complete sentences must also end in a period.

All code and comments must be word-wrapped at 100 characters.

• Tests: pytest with pytest-mock and pytest-cov

Module Structure