Closed
Conversation
Member
Author
|
in attempting to fix circle, now we have pip-dependency-resolver hell: Details |
Member
Author
|
not certain, but seems to be triggered by neo -> quantities. Maybe installing quantities from GitHub isn't satisfying neo's requested version (quantities uses some complicated magic called versioneer, so I'm not certain what version the github install will show up as, or how it will behave with pip's version comparison machinery) |
Member
|
I would try pinning memory profiler to 0.58.0 to simplify its output, too |
Member
|
Maybe same with neo to 0.10.0. Or maybe even back to 0.9 if 0.10 is causing problems |
Member
Author
|
hypothesis confirmed: |
Member
Author
|
this fix isn't going to work. The invalid backslash has been in
|
6 tasks
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
aptinstead ofapt-get(seems to fix problems due to recent debian-buster version bump, not sure why)