ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #pypi
Goal Reduce bandwidth and storage costs for a low‑traffic Python deployment by reusing the same wheel files across repeated installs. Unresolved Behavior When a dependency’s minor version changes, pip’s internal cache key may change even if the wheel file is identical. This can trigger a cache miss and cause an unnecessary download from PyPI, negating the co
PyPI implements PEP 592 yanking, which lets a maintainer mark a release as yanked with a free-form reason without removing the files. The marker is exposed via the project JSON API and on the project page. Under PEP 592 semantics, installers that support the convention generally avoid yanked releases when resolving a version range, while still permitting ins
I'm building a small client that reads release metadata from PyPI's JSON API ( /pypi/<project>/json ) and displays each file's upload time converted to the viewer's regional time zone. The API exposes two timestamp fields per release file: the legacy upload_time string and upload_time_iso_8601 , which is documented as the preferred field and carries a
The Simple API format is changing under Warehouse from legacy HTML to a PEP 691 JSON representation while keeping the same /simple/ path. The affected feature is package index access, where clients may receive JSON instead of HTML and pagination shifts from page query parameters to Link header based pagination. Authentication for uploads has also moved towar
Goal Develop a client that can gracefully handle cancellation and timeout scenarios when retrieving package metadata from the PyPI JSON API. Constraints and Uncertainty The API returns a 404 Not Found with a JSON body containing "Not found" for non‑existent packages, and a 429 Too many requests when the rate limit (~60 req/min) is exceeded. No timeout header
When pip connects to pypi.org over HTTPS, it validates the server's TLS certificate against a trusted CA bundle. If that chain cannot be established, the client aborts with SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate . The failure is well documented, yet the exact trust store pi
The supported feature under review is pip editable installs and how they interact with PyPI distribution artifacts. The goal is to clarify the expected behavior when a dependency graph developed with editable requirements is intended for reproducible installation from PyPI. Editable installs reference a local source tree and are common in development workflo
Goal Determine whether pip's verbose installation output or the PyPI JSON API provides more reliable information for diagnosing why a package failed to deploy from PyPI. Constraints and uncertainty Pip's verbose logs show each step of dependency resolution and HTTP interaction, but the level of detail varies between pip versions, and logs may not capture iss
When building an automated release client for PyPI, the goal is to retry distribution uploads after transient network failures without creating duplicate artifacts or masking genuine build errors. PyPI's legacy upload API returns HTTP 409 Conflict when a file already exists, and tools such as Twine interpret this response as a signal to skip the upload. This