-
Notifications
You must be signed in to change notification settings - Fork 0
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
AcquisitionBase - missing 'step_name' in constructor __init__ #8
Labels
Comments
reverted and reopened as it breaks things for other people |
thefab
added a commit
to metwork-framework/mfext
that referenced
this issue
Jun 23, 2021
mergify bot
pushed a commit
to metwork-framework/mfext
that referenced
this issue
Jun 23, 2021
See metwork-framework/acquisition#8 (cherry picked from commit 91a5869) # Conflicts: # .metwork-framework/components.md # layers/layer2_python3/0500_extra_python_packages/requirements3.txt
mergify bot
pushed a commit
to metwork-framework/mfext
that referenced
this issue
Jun 23, 2021
See metwork-framework/acquisition#8 (cherry picked from commit 91a5869) # Conflicts: # .metwork-framework/components.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Metwork 1.0, variable
step_name
has been wrongly removed from the constructor, so that when in some case (1), the_get_logger
function failed :step_name
is only defined in_init
function which is called byrun
functionI 'm using a plugin (AmqpSubscriber class) which inherits from
AcquisitionListener
(almost same as Metwork listener).(1) when I run my units tests, so the
run
function ofAcquisitionListener
is not called ad also the_init
andstep_name
is not defined ... and my unit tests failedAcquisitionBase Metwork 1.0
AcquisitionBase Metwork 0.9
So, it would be nice to add
self.step_main = None
in the ctor__init__
of theAcquisitionBase
class. What do you think about ?I think the 'well done' way in python, is to declare class variables in the ctor and this prevents me from declaring
step_name
in my own class to avoid issues. SinceAcquisitionListener
is a daemon,step_name
is not used in this case, I think.The text was updated successfully, but these errors were encountered: