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.

Sign up for GitHub

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

Jump to bottom

Move _system_power_bounds methods out of the *Pools and into separate classes #907

Open
shsms opened this issue Mar 28, 2024 · 0 comments
Open

Move _system_power_bounds methods out of the *Pools and into separate classes #907

shsms opened this issue Mar 28, 2024 · 0 comments
Labels
type:enhancement New feature or enhancement visitble to users type:tech-debt Improves the project without visible changes for users
Milestone
post-v1.0

Comments

@shsms
Copy link
Contributor

shsms commented Mar 28, 2024

What's needed?

These methods live in the *Pool classes, which are public interfaces, so these methods have to be private.

They are used internally by the PowerManager and they depend on the output of the PowerDistributor. We need to investigate how they can be moved into their own classes, while keeping the dependency chain.

Proposed solution

No response

Use cases

No response

Alternatives and workarounds

No response

Additional context

No response
@shsms shsms added type:enhancement New feature or enhancement visitble to users type:tech-debt Improves the project without visible changes for users labels Mar 28, 2024
@shsms shsms added this to the post-v1.0 milestone Mar 28, 2024
@shsms shsms mentioned this issue Mar 28, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:enhancement New feature or enhancement visitble to users type:tech-debt Improves the project without visible changes for users
Projects
Python SDK Roadmap
Status: To do
Milestone
post-v1.0
Development

No branches or pull requests
1 participant
@shsms