-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 from poetry add Naked #1985
Comments
Update: I discovered why this is occurring: There's a reported issue where The fix is in master but not released (as of 0.1.31) |
I have the same problem with adding my package with I have a dependency on I was able to find this installing my package into a clear venv and using
But is there another solution rather than making PRs to each individual package to fix this? This dependency loop is trivial and can be ignored on poetry level. Wouldn't it be better solution? |
|
I think that I get the same problem with networkx.
|
@MadHatt3rs this succeeds for me in $ [email protected] add networkx
Using version ^2.5 for networkx
Updating dependencies
Resolving dependencies... (0.1s)
Writing lock file
Package operations: 2 installs, 0 updates, 0 removals
• Installing decorator (4.4.2)
• Installing networkx (2.5) @gaozhidf so does $ [email protected] add pystray
Using version ^0.17.1 for pystray
Updating dependencies
Resolving dependencies... (1.2s)
Writing lock file
Package operations: 4 installs, 0 updates, 0 removals
• Installing six (1.15.0)
• Installing pillow (7.2.0)
• Installing python-xlib (0.28)
• Installing pystray (0.17.1) Regardig the assertion error, I agree this needs to be improved. |
@abn , I was using version 1.1.0, but I realized that the problem is that I created a new project with same name of the package. I did this 😅 :
I tried with another project name and it works, thanks! 😁 I think that it is not a big problem, but will be nice if there is a warn message. |
@sdispater can we get these, original issue and cyclic dependencies, propagated as a |
@MatheusR42 I did the same mistake as you did! Silly for sure, but would be nice if there was an alternative error handling when installing a package that has the same name as the project 😅 |
I made the same mistake as @MatheusR42. I wanted to play around with |
@gaozhidf, You cannot create a project with the same name of a module dependency. |
I have faced the same problem using version 1.1.12. IMHO, just a simple message explaining the cause would do much better than empty AssertionError. |
Today:
seems good to close |
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. |
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: macOS 1015.3 Catalina
Poetry version: 1.0.3
Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/shangxiao/50d1f8aa24157a14f759110b552df202
Issue
Running
poetry add Naked
results in anAssertionError
The text was updated successfully, but these errors were encountered: