renovate does not honor wildcard in version negation in python dependencies

[commonism]

How are you running Renovate?

A Mend.io-hosted app

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

Hi,

even though a specific version is excluded:

dependencies = [
    "pydantic!=2.10.*"
]

renovate wants to use it:

fix(deps): update dependency pydantic to v2.10.4

    Schedule: ["at any time"]
    Branch name: renovate/pydantic-2.x
    Merge into: master
    Upgrade [pydantic](https://redirect.github.com/pydantic/pydantic) to ==2.10.4
    Upgrade [pydantic](https://redirect.github.com/pydantic/pydantic) to !=2.10

Logs (if relevant)

No response

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[rarkins]

Do you expect renovate to ignore such dependencies?

[commonism]

To my understanding update dependency pydantic to v2.10.4 ignores pydantic!=2.10.*.

I'd prefer renovate not to ignore this.

[rarkins]

What do you expect renovate to do instead? Eg never update this constraint?

[commonism]

Update with anything but 2.10.*

[rarkins]

So you'd be happy if it updated it to =2.11.0 once available?

[commonism]

My expectation here was wrong.

I'd need it to honor the pyproject dependency definitions without updating them, and only update the uv lockfile.
This would to manually define exclusions and receive updates.
From my current understanding, this is not possible with renovate, as it updates all lockfiles?

[commonism]

I'm not sure if this is expected behavior, I think rewriting the version requirement breaks it.

https://github.com/commonism/aiopenapi3/pull/316/files