python-poetry / python-poetry/poetry

publish command doesn't publish to PyPI despite showing no errors

Open
#3,397 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/publishing kind/bug status/triage
Dominant language
Python
Stars
34.3k
Forks
2.5k
Avg merge
2d 19h
Merged PRs (30d)
30

Description

  • I am on the latest Poetry version.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).
  • Linux 5.4.0-53-generic XUbuntu 20.04 x86_64 GNU/Linux:
  • Poetry version 1.1.4:
  • Link of a Gist with the contents of your pyproject.toml file:

Issue

I have an issue with poetry not publishing the package to PyPI. The project is called dpaster, however the PyPI repo name is called thepaster. I've configured it to point to the remote repository:

The output of config command:

$ poetry config --list
cache-dir = "/home/alex/.cache/pypoetry"
experimental.new-installer = true
installer.parallel = true
repositories.dpaster.url = "https://pypi.org/project/thepaster"
virtualenvs.create = true
virtualenvs.in-project = null
virtualenvs.path = "{cache-dir}/virtualenvs"  # /home/alex/.cache/pypoetry/virtualenvs

The output of publish command:

$ poetry publish -r dpaster -vvv

Username: adder46
Password: 
Publishing dpaster (3.2.2) to dpaster
 - Uploading dpaster-3.2.2-py3-none-any.whl 100%
 - Uploading dpaster-3.2.2.tar.gz 100%

As you can see, it doesn't report any error, however, the project ends up not getting published.
I realize it works when the name in pyproject.toml is the same as the remote repository repo name, but IMO this should throw an error if it's not getting published.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the publish command and its repository configuration handling, using the provided dpaster and thepaster setup as a reproduction case. Run poetry publish -r dpaster -vvv and inspect whether the configured URL is accepted as a package endpoint. Done means the name mismatch is handled explicitly instead of reporting a successful upload when the package is not published.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.