Introduce uv

[stankudrow]

This PR introduces uv - a unified Python package manager from Astral team - authors of the famous ruff linter.

This PR:

• addresses (partially) the issue Still being maintained??? #127 ;
• reconsiders the PR Add pyproject toml file backended with pdm manager for python >= 3.9 #126 ;
• takes into account the changes from the PR Remove py2 support #130 .
• UPD: good to go after Remove py2 compatibility #136 ( @ChrisBarker-NOAA )

References:

• uv docs
• the pyproject.toml from python-multipart project (mentioned here)

[Kludex]

We need to find a way to emit the same warning. Maybe an import loader, I'm not sure. But it's the most important part here.

[stankudrow]

Could you remind, please, what warning?

[Kludex]

My comment is on the setup.py file. There's a warning there...

[ChrisBarker-NOAA]

once this goes through, there will be no setup.py file -- so ????

[Kludex]

So it needs someone to investigate how the same behavior can be maintained.

[stankudrow]

@ChrisBarker-NOAA , hello, I need your review as well.

[ChrisBarker-NOAA]

I think the only stopper here is cleaning up the license issues, otherwise, just some thoughts :-)

[ChrisBarker-NOAA]

I think we should keep this as is for now -- but the next step would be to introduce some dynamic versioning.

Hatch seems to prefer using its "version" command:

https://waylonwalker.com/hatch-version/

https://hatch.pypa.io/1.2/version/

Personally, I like there to be a __version__ string in the __init__.py.

I know that's a bit controversial, but it doesn't really harm anything, as long as it's all dynamically managed -- I think you can do that with hatch version by:

[tool.hatch.version]
path = "bson/__init__.py"

but I haven't tested it.

Anyway, I don't think we need to hold up this PR for that -- it can come later with some more thought and experimentation.

[ChrisBarker-NOAA]

NOTE: just tested it, telling hatch to find the version in __init__.py works fine -- so I think this is the way to go.

[ChrisBarker-NOAA]

once this goes through, there will be no setup.py file -- so ????

[ChrisBarker-NOAA]

I think authorship and licensing needs some cleanup -- but no need to delay this PR for that -- merge away!