Add realm attribute to Model classes

[Ryan J Ollos]

The proposed change is a refactoring to add a realm attribute to Model and ResourceManager classes. In some cases, the attribute already exists: tags/trac-1.0.1/trac/wiki/model.py?marks=33#L30​.

Previously discussed in ​th:comment:8:ticket:11706.

[Ryan J Ollos]

Adding realm to IResourceManager classes doesn't seem to make sense given that they can be associated with multiple realms: tags/trac-1.0.1/trac/versioncontrol/api.py@:367-369#L364​.

However the change for model classes probably makes sense. In Bloodhound there is a ModelBase class with a realm attribute, which is the first point that had me looking into this change.

Proposed changes in log:rjollos.git:t11609.

[Jun Omae]

Looks good to me. I think we could also add the same attribute to Attachment, Repository, Changeset and Node models. See [0a45ce96/jomae.git].

[Ryan J Ollos]

Thanks for the additional changes. Component and Version in trac/ticket/model.py will probably have a realm attribute added when #1233 is implemented.

Should we have a model.py module in trac/versioncontrol for Repository, Changeset and Node models? That might give us a more consistent structuring of the modules.

Committed to trunk in [12776].

[Jun Omae]

Replying to rjollos:

Should we have a model.py module in trac/versioncontrol for Repository, Changeset and Node models? That might give us a more consistent structuring of the modules.

Agreed. If these models are moved to model.py, I think we should add from trac.versioncontrol.model import Repository, Changeset, Node in api.py for backward compatibilities.

[Ryan J Ollos]

Replying to jomae:

Agreed. If these models are moved to model.py, I think we should add from trac.versioncontrol.model import Repository, Changeset, Node in api.py for backward compatibilities.

Thanks. I'll make the changes in #11610.