Local Pypi server - download packages on first encounter

Hi @Omri.A, thank you for posting this idea.

I'm not sure I fully understand the scenario. All our OOB packages are available in our download center to be used in offline deployments. Once you place a specific python package in the Local Pypi repository folder it will use only this version, meaning that if a newer version is released it won't be used even if you have access to the internet. This behavior as intentional.

Can you clarify the issue you encountered and your suggestion?

Alona.

the suggestion aims to make it more user friendly, by taking out the manually download requirements part. and allowing the server to download every package on first encounter.

e.g. Shell request "cloudshell-package==1.2" which is not present on the local pypi, the package will be downloaded there first.

on a 2nd Shell version, it might require version 1.3, which is not present on the local server and will get downloaded on first run.

for open versions, just pick the latest.

I think what @Omri.A is talking about is that whenever a package does not exist on the local pypi server - it will get downloaded to it, so that next time, it will be available.

Both in cases that it's completely missing, or when a specific version is missing.

While this is not available today, maybe pypi-uploader can be used to make updates to the local pypi server.

For example:

pypiupload requirements requirements.txt -i http://localpypiserver:8036

Which will first download the relevant packages to the local pypi, and then when the install requirements happen, everything will be available there.

Yaniv

Hi @Omri.A and @Yaniv.K, thank you for the clarifications. The current behavior is intentional. We do not want to automatically download a specific missing version of a package if another version already exists in the local pypi. This way we allow "locking" the version of the package.