Search results

Reference the source reasoning for each scenario

Status: Open.

#174 In astral-sh/packse;

· notatallshaw opened on Apr 14, 2024

Break up and/or build JSON scenarios from code

Status: Open.

#173 In astral-sh/packse;

· notatallshaw opened on Apr 14, 2024

"transitive-package-only-prereleases-in-range" doesn't follow the spec

Status: Open.

#171 In astral-sh/packse;

· notatallshaw opened on Apr 14, 2024

Add scenarios based on legacy versions and legacy specifiers

Status: Open.

#168 In astral-sh/packse;

· notatallshaw opened on Mar 30, 2024

packse not servering yanked packages as yanked in simple api

Status: Open.

#165 In astral-sh/packse;

· notatallshaw opened on Mar 17, 2024

Feature Request: Have packse support every version of Python that it's scenarios run against

Status: Open.

#164 In astral-sh/packse;

· notatallshaw opened on Mar 17, 2024

Feature Request: Default sdist: false where not specified in scenario

Status: Open.

#163 In astral-sh/packse;

· notatallshaw opened on Mar 16, 2024

Trying to understand "package-only-prereleases-boundary" scenario

Status: Open.

#161 In astral-sh/packse;

· notatallshaw opened on Mar 16, 2024

Scenarios with ambigious solutions with respect to the spec?

Status: Open.

#160 In astral-sh/packse;

· notatallshaw opened on Mar 16, 2024

Include scenarios in published package and have a way to point to them?

Status: Open.

#146 In astral-sh/packse;

· notatallshaw opened on Mar 8, 2024

Use content-hashes for template versioning

Status: Open.

#28 In astral-sh/packse;

· zanieb opened on Dec 14, 2023

Scenario: Backtracking with many versions

Status: Open.

#27 In astral-sh/packse;

· zanieb opened on Dec 14, 2023