-
Notifications
You must be signed in to change notification settings - Fork 9
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
Create actor factory #26
Conversation
paseos/actors/base_actor.py
Outdated
|
||
self._communication_devices = DotMap(_dynamic=False) | ||
|
||
def get_local_time(self) -> pk.epoch: |
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.
Is it not more natural to use getters? See this conversation in Stackoverflow: https://stackoverflow.com/questions/2627002/whats-the-pythonic-way-to-use-getters-and-setters#:~:text=%2B500-,What%27s%20the%20pythonic%20way%20to%20use%20getters%20and%20setters%3F,-The%20%22Pythonic%22%20way
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.
changed everywhere :) forgot about this feature, thanks for pointing out!
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.
Looks good. :)
self._known_actors = {} | ||
|
||
def remove_known_actor(self, actor_name: str): |
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.
Right now we are only distinguishing actors based on their names. I think it would make sense to make this a bit more general and use the a hash of the static features in the actors. I will write an issue for this.
Description
Summary of changes
Resolved Issues
How Has This Been Tested?
With updated tests.
Related Pull Requests
N/A