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

check up-to-date with not broken versions only #1849

Merged
merged 4 commits into from
Feb 25, 2024

Conversation

jaimergp
Copy link
Member

@jaimergp jaimergp commented Feb 24, 2024

Checklist

  • Added a news entry

Closes #1848

@jaimergp jaimergp requested a review from a team as a code owner February 24, 2024 12:32
@@ -2188,17 +2188,17 @@ def _load_forge_config(forge_dir, exclusive_config_file, forge_yml=None):
return config


def get_most_recent_version(name):
def get_most_recent_version(name, only_not_broken=False):
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't this be the unconditional default, i.e. not add another parameter?

Copy link
Member

Choose a reason for hiding this comment

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

At a minimum, think the default value should be True. Choosing to include broken packages should be opt-in (as it is with installing them)

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, changed the kwarg to include_broken=False.

@jakirkham
Copy link
Member

Thanks Jaime! 🙏

Agree with others on the line above

Otherwise think this is a welcome improvement. Thanks again for putting it together 🙂

@jakirkham jakirkham mentioned this pull request Feb 25, 2024
@xhochy xhochy merged commit 80d5aab into conda-forge:main Feb 25, 2024
2 checks passed
@h-vetinari
Copy link
Member

The include_broken kwarg doesn't seem to be wired up anywhere? It doesn't hurt for now (so fine to release 3.31.1), but I think we should either remove the kwarg completely, or ensure it can be used from CLI.

@jakirkham
Copy link
Member

Should we move that to an issue so we don't forget?

@xhochy
Copy link
Member

xhochy commented Feb 26, 2024

Should we move that to an issue so we don't forget?

Done.

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.

Soften up-to-date check
4 participants