Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

poetry build for source naming convention changed between version 1.2.0 and 1.2.1 #7314

Closed
3 tasks done
Dr-Irv opened this issue Jan 7, 2023 · 4 comments
Closed
3 tasks done
Labels
kind/question User questions (candidates for conversion to discussion)

Comments

@Dr-Irv
Copy link

Dr-Irv commented Jan 7, 2023

  • I am on the latest stable Poetry version, installed using a recommended method.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have consulted the FAQ and blog for any relevant entries or release notes.
  • [N/A ] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.

Issue

We use poetry to build pandas-stubs.

With poetry version 1.2.0, when we do poetry build, we would get the following files:

Building pandas-stubs (1.5.2.230105)
  - Building sdist
  - Built pandas-stubs-1.5.2.230105.tar.gz
  - Building wheel
  - Built pandas_stubs-1.5.2.230105-py3-none-any.whl

With poetry version 1.2.1 and above, when we do poetry build, we get the following files:

Building pandas-stubs (1.5.2.230105)
  - Building sdist
  - Built pandas_stubs-1.5.2.230105.tar.gz
  - Building wheel
  - Built pandas_stubs-1.5.2.230105-py3-none-any.whl

Note the change in the sdist of the source, where it used to be pandas-stubs, and now it is pandas_stubs. In other words, it used to include a hyphen, and now it is an underscore.

Is this a documented and intentional change? For stubs packages, it isn't a great thing!

@Dr-Irv Dr-Irv added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Jan 7, 2023
@neersighted
Copy link
Member

Yes, this was an expected fix for #5782 that brings Poetry in compliance with PEP 625. This was fixed in poetry-core 1.3.0.

However, poetry-core 1.3.0 was not brought in to the Poetry tree before Poetry 1.2.2 -- I suspect you may have mixed up the versions when you were testing this, unless something truly odd is going on.

@Dr-Irv
Copy link
Author

Dr-Irv commented Jan 7, 2023

Yes, this was an expected fix for #5782 that brings Poetry in compliance with PEP 625. This was fixed in poetry-core 1.3.0.

OK thanks for confirming. Was that change documented anywhere?

@neersighted
Copy link
Member

In the poetry-core release notes I linked, which link to the PR that changed it, python-poetry/poetry-core#484. Note that Poetry 1.2.2 predates our new practice of including poetry-core release notes in Poetry's own release notes -- Poetry 1.2.2 requires you to click through to see the release notes.

@Dr-Irv Dr-Irv closed this as completed Jan 9, 2023
@neersighted neersighted added kind/question User questions (candidates for conversion to discussion) and removed kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Jan 10, 2023
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/question User questions (candidates for conversion to discussion)
Projects
None yet
Development

No branches or pull requests

2 participants