Python Remote repos with PyPi upstream to support either `data-requires-python` or `requires-python` provided by the Simple Repository API [366058019]

Assigned

Feature Request

Status Update

No update yet.

Description

to...@google.com

created issue #1

Sep 11, 2024 10:33PM

Summary

Currently, a Python Artifact Registry remote repository with PyPi as the configured upstream will always pull the latest package that satisfies a pip install requirement. It does not take into account a client's python version which may not be compatible with the latest version of a package.

Ask

Python Artifact Registry remote repositories with PyPi as the configured upstream should support either data-requires-python or requires-python provided by the Simple Repository API, so that the latest package version supported by a given client's python version is installed (instead of always the latest that satisfies a pip install requirement)

Workaround

Clients can pin python library versions that they install on older versions of python. Alternatively, using a newer python version may avoid package incompatibility issues depending on the package being installed.

Comments

br...@calicolabs.com <br...@calicolabs.com> #2Sep 18, 2024 06:56PM

Hi, could you please share screen shots of the UI you refer? Currently in the Cloud Source Repositories UI, in the top you will find:

YourRepository > Branch > file

You have a drop down in Repository and in Branch to change anytime.

Message last modified on Sep 18, 2024 07:32PM

br...@calicolabs.com <br...@calicolabs.com> #3Sep 19, 2024 05:46PM

Hey! Thanks for taking a look at this. I have attached a screenshot of the home page of a Cloud Source Repository with the UI you mentioned open. You will see the main area says "No commits on the default branch." The default branch in this case is "main" (I am assuming that Cloud Source Repositories is expecting it to be "master"). As I mentioned in my original post, this is the naming system that github recommends and that they will be using by default starting 10/1/2020 (

https://github.com/github/renaming). I refer to github as an example because the repository in the screenshot is a mirror of a github repo, that has "main" as the default branch and no "master" branch.

to...@google.com <to...@google.com> #4Sep 23, 2024 02:03PM

Hi, this feature request has been forwarded to the Source Repository product management team so that they may evaluate it. There is no timeline or implementation guarantee for feature requests. All communication regarding this feature request is to be done here.

br...@calicolabs.com <br...@calicolabs.com> #5Sep 24, 2024 05:45PM

Using master in now discourage by a Google guideline: https://opensource.google/docs/releasing/preparing/#inclusive

But not being able to switch away from master if one wants to properly use Cloud Source Repositories is working against this policy to strictly avoid it.

ri...@google.com <ri...@google.com> Oct 4, 2024 06:35PM

Reassigned to ri...@google.com.

br...@calicolabs.com <br...@calicolabs.com> #6Oct 9, 2024 08:26PM

Shouldn't this issue has a higher priority as not being able to switch away from master is working against the inclusive policy?