Use separate “publish” URL for a private PyPI feed

• I have searched the issues of this repo and believe that this is not a duplicate.
• I have searched the documentation and believe that my question is not covered.

Feature Request

We currently use Azure DevOps Artifacts and it uses two different URLs, I feel this is similar to Artifactory and other feeds.

For pulling packages, the familiar https://.../.../pypi/simple index URL is used, but for submitting packages, https://.../.../pypi/upload Is used.

I am not aware if this is common for PyPI feeds or not, it would be great if poetry could auto-detect this and use the correct URL, or at least provide a mechanism to specify a separate publish URL for the same feed.

[jtratner]

Gotcha, that’s a really helpful explanation! maybe there’s space for a --repository-url In addition to repository?

On Tue, May 26, 2020 at 02:28 xM8WVqaG [e-mail] wrote:

(not OP but same issue)

I’m not able to pass the URL in under the --repository flag. I have to define the repo first.

[]$ poetry --version Poetry version 1.0.5

[]$ poetry publish -n --build
–repository https://gitlab.com/api/v4/projects/{REPO_ID}/packages/pypi
-u token
-p REDACTED Building my_package (0.1.4)

• Building sdist

• Built my_package-0.1.4.tar.gz

• Building wheel

• Built my_package-0.1.4-py3-none-any.whl

Publishing my_package (0.1.4) to https://gitlab.com/api/v4/projects/{REPO_ID}/packages/pypi

[RuntimeError] Repository https://gitlab.com/api/v4/projects/{REPO_ID}/packages/pypi is not defined

On the CI I’m doing:

• poetry config repositories.this “https://gitlab.com/api/v4/projects/{REPO_ID}/packages/pypi”

• poetry publish -n --build -r this -u $POETRY_HTTP_BASIC_GITLAB_USERNAME -p $POETRY_HTTP_BASIC_GITLAB_PASSWORD

Automatically creating this is fine to do in a CI lifecycle that’s destroyed after but would be inappropriate to do on a local environment. We were already discouraging manually publishing builds so I’ve been pretending this is a feature!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/python-poetry/poetry/issues/2291#issuecomment-633915541, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMGHK2KO74JMUFHQ5TRE5DRTODVJANCNFSM4MF3F5YA .

[xM8WVqaG]

(not OP but same issue)

I’m not able to pass the URL in under the --repository flag. I have to define the repo first.

[]$ poetry --version
Poetry version 1.0.5

[]$ poetry publish -n --build \
      --repository https://gitlab.com/api/v4/projects/{REPO_ID}/packages/pypi \
      -u __token__ \
      -p REDACTED                                    
Building my_package (0.1.4)
 - Building sdist
 - Built my_package-0.1.4.tar.gz

 - Building wheel
 - Built my_package-0.1.4-py3-none-any.whl

Publishing my_package (0.1.4) to https://gitlab.com/api/v4/projects/{REPO_ID}/packages/pypi

[RuntimeError]
Repository https://gitlab.com/api/v4/projects/{REPO_ID}/packages/pypi is not defined

On the CI I’m doing:

- poetry config repositories.this "https://gitlab.com/api/v4/projects/{REPO_ID}/packages/pypi"
- >
  poetry publish -n --build
  -r this
  -u $POETRY_HTTP_BASIC_GITLAB_USERNAME
  -p $POETRY_HTTP_BASIC_GITLAB_PASSWORD

Automatically creating this is fine to do in a CI lifecycle that’s destroyed after but would be inappropriate to do on a local environment. We were already discouraging manually publishing builds so I’ve been pretending this is a feature!