strip backend instances of setattr, more uses of cached_property for backend methods

[piotrbartman]

formulae or Storage should never be overridden

[slayoo]

@piotrbartman, hopefully this PR finally achieves the intended "strict" behavior - formulae should not be alterable anymore neither in the backend, nor in particulator instances. Please have a look.

[slayoo]

@abulenok, one more piece of rationale behind the non-pythonic removal of __setattr__ is that as a result the following typo-call causes an error (while without it, it passes silently producing no error and no effect):

backend.formulea = Formulae(constants={...})

(note the typo in property name)

[abulenok]

@abulenok, one more piece of rationale behind the non-pythonic removal of __setattr__ is that as a result the following typo-call causes an error (while without it, it passes silently producing no error and no effect):

backend.formulea = Formulae(constants={...})

(note the typo in property name)

@slayoo yeah, but this is true for any object in Python

[slayoo]

@abulenok, one more piece of rationale behind the non-pythonic removal of __setattr__ is that as a result the following typo-call causes an error (while without it, it passes silently producing no error and no effect):

backend.formulea = Formulae(constants={...})

(note the typo in property name)

@slayoo yeah, but this is true for any object in Python

Indeed, which is why the pystrict package introduces @strict decorator (which we extensively use in the examples), and why Pylint would complain in such case

[github-actions]

Stale pull request message

[slayoo]

closing this one in favour of a cleaner solution to be proposed and tracked at #1369