entry_point missing from maturin published packages

[xli1996]

While looking to use ruff for bazel built projects, I found bazelbuild/rules_python#1000 (comment), which the discussion suggests that entry_point is missing from target list maybe because of maturin use scripts rather than console_scripts.

I am not familiar with rust environment, so I wonder if that is intended or there might be work around so that bazel project can rely on rules_python + the entry_point macro from pip-parse.

[messense]

maybe because of maturin use scripts rather than console_scripts

Exactly. We don't want to use console_scripts for binary to avoid the cost of starting up a python interpreter.

See also #1182