▸case-01 I ran `uv sync` in my project directory, but whenever I try executing my script, I get `ModuleNotFoundError: No module named 'agentica'`. My system terminal says Python 3.12 is installed, so I'm not sure why the package is missing. Can you help me diagnose what interpreter environment my project is actually using and guide me through fixing this import failure? | fail→fail | 9,391 | 5,519 | -41% | 1 | 1 | 0% | 1,933 | 1,300 | -33% | 0 | 0 | — |
▸case-02 I added some optional dependencies to my project that require a newer Python version, but running `uv sync --all-extras` seems to silently skip installing them. Could you investigate why the packages aren't being resolved or installed and outline the troubleshooting steps to resolve the mismatch? | fail→pass | 13,074 | 4,902 | -63% | 1 | 1 | 0% | 2,423 | 1,240 | -49% | 0 | 0 | — |
▸case-03 Our installed dependencies aren't accessible inside our project workspace despite `pip install` and `uv sync` running without throwing errors. Please inspect our environment setup, show me how to verify whether packages are available in the current context, and provide a resolution to get our setup working. | fail→fail | 11,787 | 21,432 | +82% | 1 | 1 | 0% | 2,160 | 784 | -64% | 0 | 0 | — |
▸case-04 My terminal output for python3 --version returns Python 3.12, but when running scripts inside my workspace managed by uv, third-party packages fail to import. I'm tempted to reinstall system Python or modify my global PATH. How should I verify what Python binary is actually being executed by my project workspace? | fail→fail | 11,213 | 21,937 | +96% | 1 | 1 | 0% | 2,036 | 1,238 | -39% | 0 | 0 | — |
▸case-05 A dependency fails with missing symbol errors when running our application. A team member suggested reinstalling C compilers and debugging C-extension build flags immediately. What preliminary diagnostic command sequence should be executed first before attempting low-level build debugging? | fail→pass | 10,593 | 4,815 | -55% | 1 | 1 | 0% | 2,044 | 1,140 | -44% | 0 | 0 | — |
▸case-06 Our project requires a library that has a lower bound marker of python_version >= 3.12, but our environment is currently resolving to Python 3.11 because of an old configuration file. I tried manually installing the wheel with pip, but it gets ignored on sync. What exact shell commands will update the project pin, clean out the old venv, and sync all extras? | fail→pass | 6,838 | 2,435 | -64% | 1 | 1 | 0% | 1,306 | 683 | -48% | 0 | 0 | — |
▸case-07 We are experiencing mysterious import failures for a required dependency in our repository after running sync. Provide a step-by-step diagnostic workflow to check what interpreter is running, read the pin file, verify package status, and test the import directly. | fail→pass | 12,775 | 4,676 | -63% | 1 | 1 | 0% | 2,440 | 1,121 | -54% | 0 | 0 | — |
▸case-08 When syncing our workspace, a key package with a python_version >= 3.12 environment marker gets skipped without an error message because our environment is running Python 3.11. What is the root cause and how do we resolve this pin constraint? | fail→pass | 10,821 | 5,052 | -53% | 1 | 1 | 0% | 1,972 | 1,164 | -41% | 0 | 0 | — |
▸case-09 After running installation commands, our build script assumes the package is installed because the exit code was 0. How can we write a single non-interactive command to confirm that the package can actually be imported and print its version in the uv project context? | fail→fail | 9,758 | 3,837 | -61% | 1 | 1 | 0% | 1,612 | 957 | -41% | 0 | 0 | — |
▸case-10 I want to check if the requests package is properly recorded in my project's virtual environment. I usually run pip list | grep requests or check site-packages manually. What is the recommended uv command to display installed package metadata? | pass→pass | 6,550 | 3,725 | -43% | 1 | 1 | 0% | 1,194 | 908 | -24% | 0 | 0 | — |
▸case-11 I need to know what Python version is forcing uv to select a specific interpreter. I suspect there is a pin file in the directory. What command reads this pin file directly? | pass→pass | 7,062 | 1,819 | -74% | 1 | 1 | 0% | 1,289 | 535 | -58% | 0 | 0 | — |
▸case-12 A developer on our team claims our project is running Python 3.12 because python3 --version outputs 3.12.2 in their shell. Why is this reasoning flawed in a uv-managed project, and what command should they run instead? | pass→pass | 8,410 | 3,491 | -58% | 1 | 1 | 0% | 1,440 | 917 | -36% | 0 | 0 | — |
▸case-13 Our CI script runs uv sync and then immediately starts our test suite. Sometimes packages fail at runtime with ModuleNotFoundError even though sync returned 0. What rule should we apply before assuming an install succeeded? | pass→pass | 10,803 | 4,590 | -58% | 1 | 1 | 0% | 1,816 | 1,099 | -39% | 0 | 0 | — |
▸case-14 We hit a ModuleNotFoundError in our application. Our team is discussing modifying setup.py, tweaking environment variables, and editing sitecustomize.py. What diagnostic rule should pause all deeper debugging? | fail→pass | 8,652 | 6,642 | -23% | 1 | 1 | 0% | 1,320 | 1,456 | +10% | 0 | 0 | — |
▸case-15 We are upgrading a Django project that requires Python 3.12 for its new async extras, but our project root has a file setting Python to 3.11. Show the shell sequence to update the version pin, clear the existing environment, build a new venv, and sync all extras. | pass→pass | 8,735 | 2,318 | -73% | 1 | 1 | 0% | 1,732 | 713 | -59% | 0 | 0 | — |
▸case-16 I installed Python 3.13 via homebrew on macOS. When I execute python3 in my terminal, it shows 3.13.0. But inside my project, third-party modules installed via uv aren't available. Why does my project binary differ from my terminal binary? | fail→pass | 9,627 | 7,253 | -25% | 1 | 1 | 0% | 1,744 | 1,654 | -5% | 0 | 0 | — |
▸case-17 Write a shell one-liner to verify that the pydantic package is importable in our uv workspace and print its version string. | pass→pass | 3,278 | 2,975 | -9% | 1 | 1 | 0% | 539 | 537 | -0% | 0 | 0 | — |
▸case-18 We noticed that when running uv sync --all-extras, optional packages marked for Python >= 3.12 are silently omitted. What file in the workspace is restricting the resolver from installing these optional dependencies? | pass→pass | 10,618 | 3,665 | -65% | 1 | 1 | 0% | 2,028 | 839 | -59% | 0 | 0 | — |
▸case-19 When troubleshooting missing dependencies in a workspace, what is the correct ordering of diagnostic checks regarding interpreter version, version pin, package presence, and runtime import? | fail→pass | 10,591 | 3,687 | -65% | 1 | 1 | 0% | 1,804 | 935 | -48% | 0 | 0 | — |
▸case-20 We are configuring a Python package using Poetry in pyproject.toml. We need to define build-system requirements, project dependencies under [tool.poetry.dependencies], and dev dependencies. How should we format the pyproject.toml file for Poetry? | pass→pass | 9,710 | 8,195 | -16% | 1 | 1 | 0% | 1,984 | 1,933 | -3% | 0 | 0 | — |
▸case-21 We are writing a Dockerfile for a Python web application using multi-stage builds with official python:3.12-slim base images. Show how to copy wheel files from the builder stage into the final image and set up the PATH environment variable. | pass→pass | 11,388 | 9,266 | -19% | 1 | 1 | 0% | 2,313 | 2,102 | -9% | 0 | 0 | — |
▸case-22 Our C extension module fails during setup.py build_ext because CPython header files (python.h) are missing on Ubuntu. How do we install the Python C development headers via apt-get? | pass→pass | 6,257 | 3,969 | -37% | 1 | 1 | 0% | 1,202 | 920 | -23% | 0 | 0 | — |