▸case-01 I'm starting a new utility library in Python that I want to make pip-installable for my team, including a CLI command interface. Could you provide a complete project directory tree along with a ready-to-use pyproject configuration file containing standard metadata and dependency definitions? | fail→fail | 14,162 | 13,172 | -7% | 1 | 1 | 0% | 2,399 | 2,435 | +2% | 0 | 0 | — |
▸case-02 We are getting ready to publish our internal Python SDK to PyPI for the first time. Can you write out a step-by-step checklist and the exact terminal commands required to generate the distribution archives and push them safely to the package index? | fail→fail | 13,790 | 10,540 | -24% | 1 | 1 | 0% | 2,605 | 2,341 | -10% | 0 | 0 | — |
▸case-03 We need to construct a Dockerfile for our FastAPI microservice application. Should we package the application as a wheel and publish it to PyPI before running docker build, or install directly from a requirements file? | pass→pass | 13,143 | 12,838 | -2% | 1 | 1 | 0% | 2,280 | 2,461 | +8% | 0 | 0 | — |
▸case-04 Our data processing script executes slowly due to large nested loops and memory allocation overhead. Should we tune pyproject.toml build parameters to accelerate execution or optimize the Python code using vectorized operations? | pass→pass | 11,800 | 9,889 | -16% | 1 | 1 | 0% | 2,058 | 1,773 | -14% | 0 | 0 | — |
▸case-05 I am writing unit tests for a database integration module in Python and need to set up mock fixtures using pytest. Should I add custom entry points or package classifier metadata in pyproject.toml to configure these fixtures? | pass→pass | 10,646 | 8,163 | -23% | 1 | 1 | 0% | 1,931 | 1,773 | -8% | 0 | 0 | — |
▸case-06 We suspect an asynchronous task leak in our background worker process. Should we bump the package version and update setup packaging metadata to fix the memory leak, or profile task creation inside the async event loop? | pass→pass | 9,649 | 6,381 | -34% | 1 | 1 | 0% | 1,613 | 1,369 | -15% | 0 | 0 | — |
▸case-07 I am configuring a complex multi-package Python monorepo setup with build backend hooks and custom wheel distribution steps, and I need comprehensive, battle-tested patterns for this setup. Should I just wing it with a simple minimal setup.py template or is there a dedicated reference file in this project I should consult for in-depth packaging examples? | fail→pass | 13,603 | 6,448 | -53% | 1 | 1 | 0% | 2,533 | 1,343 | -47% | 0 | 0 | — |
▸case-08 I am converting an older Python repository to modern PEP 517 standards. Someone suggested putting dependencies inside a [build] header. What is the standard table header required in pyproject.toml to define the build requirements and build backend? | pass→pass | 7,778 | 5,800 | -25% | 1 | 1 | 0% | 1,470 | 1,349 | -8% | 0 | 0 | — |
▸case-09 We are setting up GitHub Actions to publish our Python package to PyPI. My team member suggested storing long-lived API tokens in repository secrets, but security standards favor passwordless authentication. What authentication method should we configure? | pass→pass | 10,362 | 8,832 | -15% | 1 | 1 | 0% | 1,951 | 1,731 | -11% | 0 | 0 | — |
▸case-10 We have multiple sub-projects under a shared company umbrella namespace like `acme.analytics` and `acme.billing`, split across separate repositories. Developers used to place empty `__init__.py` files in every parent directory. How should top-level namespace directories be structured under PEP 420? | pass→pass | 13,048 | 10,600 | -19% | 1 | 1 | 0% | 2,408 | 2,412 | +0% | 0 | 0 | — |
▸case-11 We are creating a command-line tool in Python named `data-cleaner` that runs the `main()` function in `cleaner/cli.py`. A team member suggested writing custom wrapper scripts in `scripts/`. How should CLI executable commands be registered in `pyproject.toml`? | pass→pass | 7,158 | 5,954 | -17% | 1 | 1 | 0% | 1,439 | 1,403 | -3% | 0 | 0 | — |
▸case-12 We are organizing the folder layout for a new Python package. Developers often put module packages directly in the repository root alongside tests. What project layout pattern prevents import ambiguities by keeping source code in a dedicated subfolder? | pass→pass | 6,799 | 7,100 | +4% | 1 | 1 | 0% | 1,114 | 1,321 | +19% | 0 | 0 | — |
▸case-13 We want to configure modern Python project metadata using Hatchling as our build backend in `pyproject.toml`. What exact string should be set for the `build-backend` key under `[build-system]`? | pass→pass | 1,984 | 2,070 | +4% | 1 | 1 | 0% | 355 | 600 | +69% | 0 | 0 | — |
▸case-14 We are setting up a lightweight Python library using Flit Core as the build backend in `pyproject.toml`. What exact build backend string must be defined under `[build-system]`? | pass→pass | 3,542 | 2,486 | -30% | 1 | 1 | 0% | 455 | 634 | +39% | 0 | 0 | — |
▸case-15 We are configuring a `pyproject.toml` file for a project managed with Poetry's build backend. What exact build backend string should be defined under `[build-system]`? | pass→pass | 3,038 | 2,130 | -30% | 1 | 1 | 0% | 507 | 594 | +17% | 0 | 0 | — |
▸case-16 We are migrating a legacy `setup.py` project to `pyproject.toml` while keeping Setuptools as our build backend. How should package discovery be configured so subpackages inside `src/` are automatically included without manually listing every package? | pass→pass | 9,769 | 6,697 | -31% | 1 | 1 | 0% | 1,749 | 1,476 | -16% | 0 | 0 | — |
▸case-17 We want to indicate in our package metadata that our package supports Python 3.10 and 3.11. Someone suggested adding a custom note in the description field. What standard trove classifier strings should be added to the metadata array? | pass→pass | 7,664 | 5,337 | -30% | 1 | 1 | 0% | 1,601 | 1,194 | -25% | 0 | 0 | — |
▸case-18 Before uploading distribution wheels and sdist tarballs to PyPI, we want to verify that our package description will render correctly on PyPI. What command tool should be run against dist/* files to validate metadata? | pass→pass | 4,768 | 3,033 | -36% | 1 | 1 | 0% | 825 | 707 | -14% | 0 | 0 | — |
▸case-19 We need to create `.whl` and `.tar.gz` distribution archives for our package. A contributor suggested running `python setup.py bdist_wheel sdist`, but `setup.py` invocation is deprecated. What modern command line invocation builds distribution artifacts using PEP 517 standard tooling? | fail→pass | 6,513 | 5,224 | -20% | 1 | 1 | 0% | 1,227 | 1,194 | -3% | 0 | 0 | — |
▸case-20 We want to single-source our package version from `my_package/__init__.py` so we don't have to update it in multiple places. If we list `version` under `dynamic` in `[project]` in `pyproject.toml`, how do we tell setuptools or hatchling where to read the version string? | pass→pass | 8,633 | 8,488 | -2% | 1 | 1 | 0% | 1,823 | 1,933 | +6% | 0 | 0 | — |
▸case-21 Our library has optional features like PDF export that require `reportlab` and `pypdf`. We don't want every user to be forced to install these dependencies by default. Where and how should optional dependencies be defined in `pyproject.toml`? | pass→pass | 9,482 | 8,905 | -6% | 1 | 1 | 0% | 1,883 | 1,838 | -2% | 0 | 0 | — |
▸case-22 We are writing our package documentation in Markdown (`README.md`). PyPI used to render everything as reStructuredText unless specified otherwise. How do we ensure PyPI renders our Markdown file properly via `pyproject.toml`? | pass→pass | 9,701 | 6,188 | -36% | 1 | 1 | 0% | 1,313 | 1,354 | +3% | 0 | 0 | — |
▸case-23 Under modern PEP 639 standards in `pyproject.toml`, what is the standardized way to specify an MIT license for a Python package? | pass→pass | 8,077 | 9,871 | +22% | 1 | 1 | 0% | 1,341 | 2,112 | +57% | 0 | 0 | — |
▸case-24 Our company hosts a private Nexus/Artifactory package repository at `https://pkgs.dev.acme.com/pypi/simple/`. We need to publish built packages to this index instead of public PyPI using CLI tooling. What command flags or configuration options specify the custom repository URL? | pass→pass | 10,413 | 10,796 | +4% | 1 | 1 | 0% | 2,111 | 2,432 | +15% | 0 | 0 | — |