-
Notifications
You must be signed in to change notification settings - Fork 36
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
dependency info doesn't clue circup to install connection manager #157
Comments
That is odd. My understanding of circup was that it checks requirements.txt for any dependencies deployed to pypi, and then checks pyproject.toml for a specific value that can contain dependencies which exist in a bundle but not on pypi. It does look like connection manager is listed correctly in the requirements file:
I'm pretty sure I saw someone mention in discord yesterday that they downloaded a project bundle from learn and it did properly contain ConnectionManager but I could have gotten wires crossed, I was not actively involved in the conversation. It does look like circup isn't currently able to install connection manager directly either though, so perhaps our issue is deeper than just this libraries dependencies being properly linked.
|
I think maybe whats happened is a mismatch of the expected library name. When connection manager gets imported in code it's imported as circup typically supports both the "import name" like The latter isn't typically used by humans, but is internally when circup fetches dependencies from requirements.txt. It looks like the "pypi name" for connection manager I'm not entire sure of the most appropriate way to resolve this situation though. It seems the naming isn't consistent with the logic that is currently within circup, so we either will need to rename it somewhere, or change the logic to try to handle this case. If possible I think changing the name so that it's consistent with all of the other libraries would be good, but I don't know how much trouble would be caused by changing it. However, if it is true that the learn project bundler can handle the naming the way it is, then perhaps it does make the most sense to update circups logic so that it's behavior matches the bundler. I know my assumption was that they did behave the same. |
I was worried about this initially when the repo was named, but saw that |
this is resolved by: adafruit/circup#201 |
I did a
circup install adafruit_requests
. Then at the repl,whatever's in the project metadata doesn't seem to have this dependency listed in a way circup understands.
The text was updated successfully, but these errors were encountered: