Due to the fact that Bugzilla's REST API isn't actually very RESTful, you can't directly update some fields by just setting the value in the PUT data. For example, when GETing a bug, the field "groups" contains a list of group names the bug is in. But to change the bug's groups, you have to pass in an object that contains "add" and/or "remove" keys. This means we either need to track it separately, or else the "groups" object in the _bug dictionary will have a different format depending on whether it is to be updated or not.
Furthermore, this would reduce both the transmission size and the time to process it.
I would suggest, rather than using a lot of @Property and @Setter decorators, overriding getattr and setattr, and, in the latter, building up a new dictionary of values to be updated, and using that in Bugsy.put().
Due to the fact that Bugzilla's REST API isn't actually very RESTful, you can't directly update some fields by just setting the value in the PUT data. For example, when GETing a bug, the field "groups" contains a list of group names the bug is in. But to change the bug's groups, you have to pass in an object that contains "add" and/or "remove" keys. This means we either need to track it separately, or else the "groups" object in the _bug dictionary will have a different format depending on whether it is to be updated or not.
Furthermore, this would reduce both the transmission size and the time to process it.
I would suggest, rather than using a lot of @Property and @Setter decorators, overriding getattr and setattr, and, in the latter, building up a new dictionary of values to be updated, and using that in Bugsy.put().