For https://teams.microsoft.com/l/message/19:b97d98e6d22c41e0970a1150b484d935@thread.skype/1756195564558?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&parentMessageId=1756195564558&teamName=Azure%20SDK&channelName=Language%20-%20Python&createdTime=1756195564558, customers are confusing why generated SDK has no difference after adding @added in new models. The reason is as Laurent said, current python emitter only add validation for operation and parameters and don't handle versioning for models. Now versioning docs doesn't explicitly contain this kind of scenario. If we could add it, maybe bot could answer the question more acurately.
For https://teams.microsoft.com/l/message/19:b97d98e6d22c41e0970a1150b484d935@thread.skype/1756195564558?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&parentMessageId=1756195564558&teamName=Azure%20SDK&channelName=Language%20-%20Python&createdTime=1756195564558, customers are confusing why generated SDK has no difference after adding
@addedin new models. The reason is as Laurent said, current python emitter only add validation for operation and parameters and don't handle versioning for models. Now versioning docs doesn't explicitly contain this kind of scenario. If we could add it, maybe bot could answer the question more acurately.