Refrain from accessing private members about qiskit-experiments HOT 4 CLOSED

Is there a way to enforce policy that forbids access to private members? Maybe using lint?

from qiskit-experiments.

Regarding linter, I think there are pros and cons of allowing private access. Basically I agree with you, we should remove unreasonable access to private members. However, making all of them public means we will have obligation to maintain the interface for end users -- if we need some spec change, we should add deprecation warning and cannot change the implementation for few months (owing to Qiskit mentenance policy). So sometime it's better to tolerate some private member access.

from qiskit-experiments.

It's a good argument, I didn't think of it. So the issue becomes just removing access to private members that already have getters and setters. Without making others public, and without activating the linter for this purpose.

from qiskit-experiments.

Closing as this is currently fixed except for members without getters and setters

from qiskit-experiments.