`maturin init/new` should validate the package name

[not-my-profile]

Package names of Rust libraries and package names of Python libraries both need to fulfill certain criteria. maturin init/new apparently currently doesn't check for any of these criteria e.g. maturin init "foo bar" works fine even though neither Rust nor Python support package names with a space.

I think ideally maturin would check the supplied name against two regexes (one for Rust package names and one for Python package names) and report which check failed in case the supplied name doesn't match.

Note that I think PyPI disallows certain package names like names of modules in the standard library ... it would be nice if maturin could check for these as well but that might not be easily doable (see also pypi/warehouse#8533).

[messense]

Agreed it's nice to have, pull requests are welcome.

[mtantaoui]

Can I please work on this one please ?

[messense]

@mahtantaoui No need to ask permission to work on issues, feel free to send pull requests, thanks!

[styvane]

Can we validate the package name using a combination of an approach similar to the one in Cargo for Rust names and the constraint in PYPI for Python?

[messense]

Can we validate the package name using a combination of an approach similar to the one in Cargo for Rust names and the constraint in PYPI for Python?

I think so, pull requests are welcome!

[sanmai-NL]

See also: rust-lang/cargo#12766

[alonme]

Can we validate the package name using a combination of an approach similar to the one in Cargo for Rust names and the constraint in PYPI for Python?

permalink to the pypi/warehouse name constraint