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

AssertionError when adding a package with same name as project #5954

Closed
3 tasks done
ierezell opened this issue Jul 5, 2022 · 2 comments
Closed
3 tasks done

AssertionError when adding a package with same name as project #5954

ierezell opened this issue Jul 5, 2022 · 2 comments
Labels
kind/bug Something isn't working as expected

Comments

@ierezell
Copy link

ierezell commented Jul 5, 2022

  • 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).
  • OS version and name:Linux 5.18.7-arch1-1
  • Poetry version: 1.1.13
  • Link of a Gist with the contents of your pyproject.toml file:
[tool.poetry]
name = "ASuperPackage"
version = "0.1.0"
description = ""
authors = [""]
 
[tool.poetry.dependencies]
python = "~3.9"
 
[tool.poetry.dev-dependencies]
 
[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"
poetry add ASuperPackage # like sagemaker (pip) vs sagemaker (the name of my poetry project)

Issue

The error is only an AssertionError which does not says why the add is failing.
After banging my head on the wall, I found out that my poetry project name was the same of the pip package I wanted to install (in my case sagemaker)

I don't know how we could solve that, maybe a more descriptive error ? A version check of the packages (sagemaker is 2.97.0, my package 0.1.0) ?

Thanks in advance,
Have a great day.

@ierezell ierezell added kind/bug Something isn't working as expected status/triage This issue needs to be triaged labels Jul 5, 2022
@finswimmer
Copy link
Member

Hey @ierezell,

this was reported earlier in #236 and was solved by #3841 which is included in the current preview release (1.2.0b2).

fin swimmer

@mkniewallner mkniewallner removed the status/triage This issue needs to be triaged label Jul 9, 2022
Copy link

github-actions bot commented Mar 1, 2024

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 Mar 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests

3 participants