Skip to content

Use the requires expression in the package manifest - #36

Merged
ru551n merged 1 commit into
VUnit:mainfrom
ru551n:manifest-requires
Oct 16, 2026
Merged

ru551n merged 1 commit into
VUnit:mainfrom
ru551n:manifest-requires

Conversation

@ru551n

@ru551n ru551n commented Oct 16, 2026 •

Copy link
Copy Markdown
Collaborator

The package manifest uses the requires expression of VUnit 5.0.0.dev15 (VUnit/vunit#1232) instead of the deprecated requires-vunit and requires-vhdl fields:

requires = 'vunit >= "5.0.0.dev15" and vhdl >= "2008"'
  • VUnit validates manifests strictly and rejects unknown fields. Older VUnit versions therefore can't read requires, and dev15 is already the minimum since Add Python dict support using VUnit dict_t #11.
  • The manifest test now checks that the VUnit version in requires matches vunit_hdl>= in pyproject.toml, so the two can't drift apart.
  • The supported simulators stay checked by the setup function, not by requires. Its error names the supported simulators and the selected one, while a requires mismatch only reports that the expression is not satisfied.

🤖 Generated with Claude Code

@ru551n
ru551n force-pushed the manifest-requires branch from 17481e9 to 0ff7747 Compare October 16, 2026 12:35
@ru551n
ru551n marked this pull request as ready for review October 16, 2026 12:51
requires-vunit and requires-vhdl are deprecated since VUnit 5.0.0.dev15
(VUnit/vunit#1232) in favour of one requires expression. The test checks
that its VUnit version is the one pyproject.toml requires.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ru551n
ru551n force-pushed the manifest-requires branch from 0ff7747 to c52bd40 Compare October 16, 2026 12:59
@ru551n
ru551n merged commit 0ae8608 into VUnit:main Oct 16, 2026
59 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant