Outdated / wrong information regarding setup.cfg

[MaxusTheOne]

Select Topic Area

Product Feedback

Copilot Feature Area

JetBrains & Xcode

Body

Wanted to provide some feedback with copilots info. But idk if this is the best place

had this in setup.cfg:

[options.extras_require] 
test =
    pytest
    pytest-cov
    pytest-qt
    codecov

dev =
    napari[all] < 0.6

And wanted "dev" to inherit (or similar) all dependencies from "test".
Copilot insisted it could not be done, and nothing similar. 3 messages in a row where I asked and it insisted.
Copilot even went so far as to instead suggest a script that updated setup.cfg, showing it did know what I wanted. (i'll paste it below)
Turns out, you can totally do it, setuptools docs -> Interpolation

Copilots "alternative" solution:

from setuptools import setup, find_packages

# Shared dependencies
test_dependencies = [
    "pytest",
    "pytest-cov",
    "pytest-qt",
    "codecov",
]

dev_dependencies = [
    "napari[all] < 0.6",
    *test_dependencies,  # Include test dependencies
]

setup(
    name="napari-pitcount-cfim",
    version="0.3.1",
    description="A pipeline for stuff",
    author="Markus L. Bille",
    author_email="github+markus@bille.dk",
    license="BSD-3-Clause",
    packages=find_packages(where="src"),
    package_dir={"": "src"},
    python_requires=">=3.9",
    install_requires=[
        "QtPy",
        "pydantic",
    ],
    extras_require={
        "test": test_dependencies,
        "dev": dev_dependencies,
    },
    entry_points={
        "napari.manifest": [
            "napari-pitcount-cfim = napari_pitcount_cfim:napari.yaml",
        ],
    },
)

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐