Skip to content

66 constraints do not seem to work when there is a calculator set #67

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

Conversation

andped10
Copy link
Contributor

Prevent the usage of eventual callback values when applying constraints

@andped10 andped10 added the [scope] bug Bug report or fix (major.minor.PATCH) label Aug 27, 2024
Copy link
Member

@rozyczko rozyczko left a comment

Choose a reason for hiding this comment

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

This looks sensible.

One minor typo: in the definition of def value_no_call_back in parameters.py
the docstring should say suppressing instead of surpassing.

@andped10 andped10 merged commit 6c25b12 into develop Aug 28, 2024
26 checks passed
@andped10 andped10 deleted the 66-constraints-do-not-seem-to-work-when-there-is-a-calculator-set branch August 28, 2024 07:14
@andped10 andped10 linked an issue Sep 2, 2024 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[scope] bug Bug report or fix (major.minor.PATCH)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Constraints do not seem to work when there is a calculator set
2 participants