René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"field \"model_flags\" conflicts with Pydantic 2 protected namespaces","articleBody":"### Environment\r\n* DiffSync version:  2.0.0\r\n* Python version  Python 3.10.12\r\n\r\n\u003c!-- What happened instead? --\u003e\r\n### Observed Behavior\r\nGetting warning logs from Pydantic about protected namespace violations within the DiffSync library\r\n\u003c!-- What did you expect to happen? --\u003e\r\n### Expected Behavior\r\nNo logging output at the warning level\r\n\u003c!--\r\n    Describe in detail the exact steps that someone else can take to reproduce\r\n    this bug using the current release.\r\n--\u003e\r\n### Steps to Reproduce\r\n1. `python3 -i`\r\n2. `from diffsync import DiffSyncModel`\r\n\r\n### Extra Information\r\n\r\nPydantic introduces protected namespaces in their new documentation that places warning logs for things like `model_` fields [documentation here](https://docs.pydantic.dev/latest/api/config/#protected-namespaces) \r\n\r\npotential workaround is to use the ConfigDict to set protected_namespaces to an empty value.\r\n```\r\nclass Device(DiffSyncModel):\r\n    \"\"\"common model used for Diffsync\"\"\"\r\n    \r\n    # Disables new Pydantic v2 protections since diffsync uses model_ fields\r\n    model_config = ConfigDict(\r\n        protected_namespaces=()\r\n    )\r\n ```\r\n \r\n However, this does not prevent the log entries from the diffsync BaseModel here:\r\n https://github.com/networktocode/diffsync/blob/13f5150d66ec76b637f56c908d1ab300bf63661d/diffsync/__init__.py#L110","author":{"url":"https://github.com/dnewood","@type":"Person","name":"dnewood"},"datePublished":"2024-02-12T20:37:32.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":13},"url":"https://github.com/267/diffsync/issues/267"}