Versioning: setuptools-scm compatibility

[miili]

Hi all,

using https://github.com/pypa/setuptools_scm for version inference from git tags streamlines and automates the publishing workflow.
Unfortunately it is incompatible with maturin and the fixed version in Cargo.toml. How can maturin leverage this automation process?

I saw closed #199, stating:

PEP 621 also commited to having a static project.version field in the metadata just like cargo's package.version, so this a won't fix from maturin's side. If you need to do this just use sed to replace the version in a previous step of the CI pipeline

But this is not right, PEP 621 encourages project.dynamic fields.

Best,

M

[messense]

Duplicate of #1267, please continue the discussion there.

[rmorshea]

Are there any plans to support similar functionality within Maturin itself?