-
Notifications
You must be signed in to change notification settings - Fork 178
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
refactor(api): Move opentrons.initialize() to its own file #15191
Conversation
api/src/opentrons/_resources_path.py
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put this in its own file to keep it close to the resources/
directory that it's referencing. Otherwise we'd be trying to access it from inside hardware_control/
with some fragile relative path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome and could even take it a step farther
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense 👍
Overview
PR #15171 runs into a circular import problem. We can fix it by paring down the contents of
api
's top-level__init__.py
, which might also have the benefit of improving performance (see explanation in PR #14480), so this does that. This goes towards EXEC-456.Test plan
None needed.
Changelog
Move
opentrons.initialize()
toopentrons.hardware_control.initialization.initialize()
, a new file.Review requests
_find_smoothie_file()
function?opentrons.should_use_ot3()
, which currently remains in the top-level__init__.py
?Risk assessment
Low.