Dev dependencies should not be extras

[bkeryan]

Converting dependency groups to extras is completely wrong. Please revert this.

Before:

Metadata-Version: 2.3
Name: nipanel
Version: 0.1.0
Summary: NI Panel Python API
Author: NI
Author-email: opensource@ni.com
Requires-Python: >=3.9, !=2.7.*, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*, !=3.5.*, !=3.6.*, !=3.7.*, !=3.8.*
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Requires-Dist: debugpy (>=1.8.1)
Requires-Dist: grpcio (>=1.49.0,<2.0)
Requires-Dist: ni-measurement-plugin-sdk (>=2.4.0dev1)
Requires-Dist: ni-panels-v1-proto (>=0.1.0dev1)
Requires-Dist: ni-protobuf-types (>=0.1.0dev2)
Requires-Dist: nitypes (>=0.1.0dev8)
Requires-Dist: numpy (>=1.22)
Requires-Dist: protobuf (>=4.21)
Requires-Dist: streamlit (>=1.24)
Requires-Dist: typing-extensions (>=4.13.2)
Description-Content-Type: text/markdown

# nipanel-python
Source for the nipanel python package

After:

Metadata-Version: 2.3
Name: nipanel
Version: 0.1.0
Summary: NI Panel Python API
Author: NI
Author-email: opensource@ni.com
Requires-Python: >=3.9,<4.0,!=3.9.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Provides-Extra: dev
Provides-Extra: docs
Provides-Extra: examples
Provides-Extra: lint
Provides-Extra: test
Requires-Dist: Sphinx (>=8.2) ; (python_version >= "3.11") and (extra == "docs")
Requires-Dist: bandit[toml] (>=1.7) ; extra == "lint"
Requires-Dist: debugpy (>=1.8.1)
Requires-Dist: extra-streamlit-components (>=0.1.80) ; extra == "examples"
Requires-Dist: grpcio (>=1.49.0,<2.0)
Requires-Dist: hightime (>=0.2.2) ; extra == "test"
Requires-Dist: m2r2 (>=0.3.2) ; extra == "docs"
Requires-Dist: mypy (>=1.0) ; extra == "lint"
Requires-Dist: ni-measurement-plugin-sdk (>=2.4.0dev1)
Requires-Dist: ni-panels-v1-proto (>=0.1.0dev1)
Requires-Dist: ni-protobuf-types (>=0.1.0dev3)
Requires-Dist: ni-python-styleguide (>=0.4.1) ; extra == "lint"
Requires-Dist: nidaqmx (>=0.8.0) ; extra == "examples"
Requires-Dist: niscope (>=1.4.9) ; extra == "examples"
Requires-Dist: nitypes (>=0.1.0dev8)
Requires-Dist: numpy (>=1.22)
Requires-Dist: numpy (>=1.22) ; (python_version >= "3.9" and python_version < "3.12") and (extra == "dev")
Requires-Dist: numpy (>=1.26) ; (python_version == "3.12") and (extra == "dev")
Requires-Dist: numpy (>=2.1) ; (python_version >= "3.13") and (extra == "dev")
Requires-Dist: protobuf (>=4.21)
Requires-Dist: pyright[nodejs] (>=1.1.400) ; extra == "lint"
Requires-Dist: pytest (>=7.2) ; extra == "test"
Requires-Dist: pytest-cov (>=4.0) ; extra == "test"
Requires-Dist: pytest-mock (>=3.0) ; extra == "test"
Requires-Dist: sphinx-autoapi (>=1.8.4) ; extra == "docs"
Requires-Dist: sphinx-rtd-theme (>=1.0.0) ; extra == "docs"
Requires-Dist: streamlit (>=1.24)
Requires-Dist: streamlit-echarts (>=0.4.0) ; extra == "examples"
Requires-Dist: toml (>=0.10.2) ; extra == "docs"
Requires-Dist: types-grpcio (>=1.0) ; extra == "dev"
Requires-Dist: types-protobuf (>=4.21) ; extra == "dev"
Requires-Dist: typing-extensions (>=4.13.2)
Description-Content-Type: text/markdown

# nipanel-python
Source for the nipanel python package

Originally posted by @bkeryan in #142 (comment)

AB#3242370

[bkeryan]

@mikeprosserni Did a migration tool like https://pypi.org/project/poetry-plugin-migrate/ do this? I would hope that such tools leave dependency groups alone.

Edit: I tried https://pypi.org/project/poetry-plugin-migrate/ on another project and it does not do this. It gives you the option to leave version, classifiers, and python-requires in the old [tool.poetry] tables. When it does this, it updates the project.dynamic table to indicate that these PEP 621-defined static keys are not specified and the build backend dynamically calculates them.

The standardized equivalent of Poetry's dependency groups is defined by PEP 735. It explains why using extras for dev dependencies is bad:

For projects which are packages, extras are a common solution for defining development dependencies, but even under these circumstances they have downsides:

• Because an extra defines optional additional dependencies, it is not possible to install an extra without installing the current package and its dependencies.
• Because they are user-installable, extras are part of the public interface for packages. Because extras are published, package developers often are concerned about ensuring that their development extras are not confused with user-facing extras.

Cc: @mshafer-NI