Making Poetry Match Exact Version Numbers

[inolaole]

Problem:
When specifying a poetry add package@version i.e. (package@0.1.4) it will match package@0.1.4-sha instead of package@0.1.4 (seems like poetry assumes anything with the extra value is later than the bare version number).

Expectation:
I would expect poetry to match my exact version number I specified rather than attempting to grab a potentially earlier or later version number

Extra Info:
I did in fact verify that the bare version package is marked as latest in our server. So it's not a matter of what is marked as latest.

Is there any syntax that will actively do what is expected? Perhaps specifying with a parameter or with the use of quotes?

[marsboy02]

Due to Poetry's version parsing method, it interprets the version as being >= 0.1.4 and < 0.1.5, and it seems to give higher priority to versions with a "-sha" identifier.

if connections with this, I found the following command in the official documentation. It is recommanded to specify the version using the following command:

poetry add 'package==0.1.4'

• Reference : https://python-poetry.org/docs/cli/#add

I hope this helps. Have a great day!

[inolaole]

Afraid that does not seem to do the trick. Looks like I'll probably have to just differentiate the version numbers in another way to prevent collision.

[radoering]

According to the standard ==0.1.4 must allow 0.1.4+sha (which is a local version) and since local versions are greater than public versions of the same release, they are preferred by Poetry.

What you want is called "arbitrary equality" by the standard and not supported by Poetry. See #7256.