Skip to content

Conversation

@ajaust
Copy link
Collaborator

@ajaust ajaust commented Mar 4, 2021

Allow for pyprecice versions that are newer than 2.0. A quick check on my local machine worked out.

That is related to #90

Closes #90

Allow for `pyprecice` that are newer than 2.0.
@ajaust ajaust requested a review from BenjaminRodenberg March 4, 2021 10:31
@ajaust ajaust self-assigned this Mar 4, 2021
Copy link
Member

@BenjaminRodenberg BenjaminRodenberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Looks good to me. I also tried installing from develop as well as from this branch and observed the same you reported in #90.

You suggested adding the missing digits in the version number. I.e. pyprecice>=2.0.0.0 instead of pyprecice>=2.0. I think that this is optional. We can even write pyprecice>=2, if we want. I don't have a opinion here. I'm fine with any of the solutions above. Feel free to merge this PR either as it is or with a four or single digit version number.

@ajaust
Copy link
Collaborator Author

ajaust commented Mar 4, 2021

Then I will leave it as 2.0 for now. If we find out that we do not like it anymore, we can still change it in the future.

@ajaust ajaust closed this Mar 4, 2021
@ajaust ajaust reopened this Mar 4, 2021
@ajaust ajaust merged commit 3b9b14d into develop Mar 4, 2021
@BenjaminRodenberg BenjaminRodenberg deleted the update-solver-dummy-req branch August 13, 2021 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Solver dummy partly out of date

3 participants